CWE · MITRE source
CWE-1230Exposure of Sensitive Information Through Metadata
The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.
Developers might correctly prevent unauthorized access to a database or other resource containing sensitive information, but they might not consider that portions of the original information might also be recorded in metadata, search indices, statistical reports, or other resources. If these resources are not also restricted, then attackers might be able to extract some or all of the original information, or otherwise infer some details. For example, an attacker could specify search terms that are known to be unique to a particular person, or view metadata such as activity or creation dates in order to identify usage patterns.
Last updated: 04 July 2026 00:28 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: mostly · 7 mapping(s) from 2 framework(s): ASVS 5.0 4 (mostly) · ATT&CK 3 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AU-13 | Monitoring for Information Disclosure | AU | Identifies sensitive information exposed via metadata during disclosure monitoring. |
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-2024-53291 | 5.5 | 7.5 | 0.0030 | 2024-12-25 |
CVE-2024-9099 | 5.5 | 8.1 | 0.0055 | 2025-03-20 |
CVE-2025-0330 | 5.5 | 7.5 | 0.0052 | 2025-03-20 |
CVE-2025-47324 UPD | 5.5 | 7.5 | 0.0017 | 2025-08-06 |
CVE-2025-13084 | 5.5 | 7.6 | 0.0024 | 2025-11-26 |
CVE-2023-1974 | 3.5 | 6.5 | 0.0060 | 2023-04-11 |
CVE-2023-32488 | 3.5 | 5.3 | 0.0032 | 2023-08-16 |
CVE-2023-6962 | 3.5 | 5.3 | 0.0044 | 2024-05-02 |
CVE-2024-8910 | 3.5 | 4.3 | 0.0031 | 2024-09-25 |
CVE-2024-49395 UPD | 3.5 | 5.3 | 0.0029 | 2024-11-12 |
CVE-2024-47517 | 3.5 | 6.8 | 0.0039 | 2025-01-10 |
CVE-2024-10324 | 3.5 | 4.3 | 0.0026 | 2025-01-24 |
CVE-2025-26527 | 3.5 | 5.3 | 0.0034 | 2025-02-24 |
CVE-2025-1921 | 3.5 | 6.5 | 0.0032 | 2025-03-05 |
CVE-2024-9447 | 3.5 | 6.5 | 0.0057 | 2025-03-20 |
CVE-2025-48941 UPD | 3.5 | 5.3 | 0.0028 | 2025-06-02 |
CVE-2026-27661 | 3.5 | 4.3 | 0.0026 | 2026-03-10 |
CVE-2026-29055 | 3.5 | 5.3 | 0.0031 | 2026-03-26 |
CVE-2026-49270 UPD | 3.5 | 5.9 | 0.0033 | 2026-06-01 |
CVE-2026-45544 UPD | 3.5 | 4.3 | 0.0022 | 2026-06-01 |
CVE-2025-59601 UPD | 3.5 | 6.5 | 0.0011 | 2026-06-01 |
CVE-2023-50458 | 1.5 | 3.5 | 0.0019 | 2025-07-10 |
CVE-2025-8713 UPD | 1.5 | 3.1 | 0.0021 | 2025-08-14 |
CVE-2025-31959 UPD | 1.5 | 3.5 | 0.0014 | 2026-05-06 |