CWE · MITRE source
CWE-202Exposure of Sensitive Information Through Data Queries
When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
In situations where data should not be tied to individual users, but a large number of users should be able to make queries that "scrub" the identity of users, it may be possible to get information about a user -- e.g., by specifying search terms that are known to be unique to that user.
Last updated: 04 July 2026 08:17 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 1 framework(s): ATT&CK 2 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-59352 | 7.0 | 9.8 | 0.0068 | 2025-09-17 |
CVE-2025-68456 | 7.0 | 9.1 | 0.0047 | 2026-01-05 |
CVE-2021-32743 | 5.5 | 8.8 | 0.0180 | 2021-07-15 |
CVE-2022-41623 | 5.5 | 7.5 | 0.0070 | 2022-10-14 |
CVE-2023-1625 | 5.5 | 7.4 | 0.0071 | 2023-09-24 |
CVE-2023-7072 | 5.5 | 7.5 | 0.0062 | 2024-03-12 |
CVE-2024-2088 | 5.5 | 8.5 | 0.0034 | 2024-05-22 |
CVE-2024-6400 UPD | 5.5 | 7.5 | 0.0061 | 2024-10-04 |
CVE-2024-13255 | 5.5 | 7.5 | 0.0049 | 2025-01-09 |
CVE-2025-25205 | 5.5 | 8.2 | 0.0383 | 2025-02-12 |
CVE-2025-29981 | 5.5 | 7.5 | 0.0034 | 2025-04-02 |
CVE-2025-36575 UPD | 5.5 | 7.5 | 0.0029 | 2025-06-10 |
CVE-2025-69200 | 5.5 | 7.5 | 0.0200 | 2025-12-29 |
CVE-2026-33530 | 5.5 | 7.7 | 0.0020 | 2026-03-26 |
CVE-2026-30778 | 5.5 | 7.5 | 0.0054 | 2026-04-15 |
CVE-2026-40245 | 5.5 | 7.5 | 0.0051 | 2026-04-16 |
CVE-2019-19000 | 3.5 | 6.5 | 0.0105 | 2020-04-02 |
CVE-2019-19091 | 3.5 | 4.3 | 0.0076 | 2020-04-02 |
CVE-2021-1372 | 3.5 | 5.5 | 0.0041 | 2021-02-17 |
CVE-2021-34782 | 3.5 | 4.3 | 0.0076 | 2021-10-06 |
CVE-2022-20747 | 3.5 | 6.5 | 0.0088 | 2022-04-15 |
CVE-2021-4159 | 3.5 | 4.4 | 0.0024 | 2022-08-24 |
CVE-2022-20810 | 3.5 | 6.5 | 0.0065 | 2022-09-30 |
CVE-2023-20215 | 3.5 | 5.8 | 0.0048 | 2023-08-03 |
CVE-2024-38892 | 3.5 | 6.5 | 0.0040 | 2024-06-24 |