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: 14 October 2026 20:41 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (1)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AU-13 | Monitoring for Information Disclosure | AU | Identifies sensitive information exposed via metadata during disclosure monitoring. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-9099 UPD | 6.2 | 8.1 | 0.0060 | 2025-03-20 |
CVE-2025-0330 UPD | 5.9 | 7.5 | 0.0057 | 2025-03-20 |
CVE-2025-13084 UPD | 5.7 | 7.6 | 0.0027 | 2025-11-26 |
CVE-2024-53291 UPD | 5.6 | 7.5 | 0.0031 | 2024-12-25 |
CVE-2025-47324 UPD | 5.6 | 7.5 | 0.0019 | 2025-08-06 |
CVE-2024-47517 UPD | 5.3 | 6.8 | 0.0040 | 2025-01-10 |
CVE-2023-1974 UPD | 5.2 | 6.5 | 0.0060 | 2023-04-11 |
CVE-2024-9447 UPD | 5.2 | 6.5 | 0.0061 | 2025-03-20 |
CVE-2025-1921 UPD | 5.0 | 6.5 | 0.0033 | 2025-03-05 |
CVE-2025-59601 UPD | 4.8 | 6.5 | 0.0011 | 2026-06-01 |
CVE-2026-49270 UPD | 4.7 | 5.9 | 0.0051 | 2026-06-01 |
CVE-2023-6962 UPD | 4.5 | 5.3 | 0.0044 | 2024-05-02 |
CVE-2023-32488 UPD | 4.4 | 5.3 | 0.0038 | 2023-08-16 |
CVE-2024-49395 UPD | 4.4 | 5.3 | 0.0031 | 2024-11-12 |
CVE-2025-26527 UPD | 4.4 | 5.3 | 0.0036 | 2025-02-24 |
CVE-2025-48941 UPD | 4.4 | 5.3 | 0.0034 | 2025-06-02 |
CVE-2026-29055 | 4.4 | 5.3 | 0.0037 | 2026-03-26 |
CVE-2026-45544 UPD | 3.7 | 4.3 | 0.0037 | 2026-06-01 |
CVE-2026-14351 | 3.7 | 4.3 | 0.0040 | 2026-07-29 |
CVE-2024-8910 UPD | 3.6 | 4.3 | 0.0031 | 2024-09-25 |
CVE-2024-10324 UPD | 3.6 | 4.3 | 0.0027 | 2025-01-24 |
CVE-2026-27661 | 3.6 | 4.3 | 0.0028 | 2026-03-10 |
CVE-2023-50458 UPD | 2.9 | 3.5 | 0.0022 | 2025-07-10 |
CVE-2025-31959 UPD | 2.9 | 3.5 | 0.0014 | 2026-05-06 |
CVE-2025-8713 UPD | 2.7 | 3.1 | 0.0024 | 2025-08-14 |