CWE · MITRE source
CWE-213Exposure of Sensitive Information Due to Incompatible Policies
The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed.
When handling information, the developer must consider whether the information is regarded as sensitive by different stakeholders, such as users or administrators. Each stakeholder effectively has its own intended security policy that the product is expected to uphold. When a developer does not treat that information as sensitive, this can introduce a vulnerability that violates the expectations of the product's users.
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 · 12 mapping(s) from 4 framework(s): ATT&CK 6 (partial) · ASVS 5.0 4 (mostly) · STIG ubuntu 24 04 1 (partial) · STIG windows server 2019 1 (partial)
NIST 800-53 r5 controls that address this weakness (3)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
PT-2 | Authority to Process Personally Identifiable Information | PT | Demands documented authority and policy alignment for PII processing, reducing exposure due to incompatible or absent policies. |
PT-3 | Personally Identifiable Information Processing Purposes | PT | Directly enforces purpose compatibility and policy alignment for PII processing, preventing exposure from incompatible policies. |
PE-22 | Component Marking | PE | Marking hardware components with the permitted impact or classification level directly supports consistent policy enforcement, reducing the chance that sensitive data is processed on an incompatible component and thereby exposed. |
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-2019-1010283 | 5.5 | 7.5 | 0.0145 | 2019-07-17 |
CVE-2022-30350 | 5.5 | 7.5 | 0.0073 | 2023-03-30 |
CVE-2023-6517 | 5.5 | 7.5 | 0.0047 | 2024-02-08 |
CVE-2026-33216 UPD | 5.5 | 8.6 | 0.0037 | 2026-03-25 |
CVE-2019-10246 | 3.5 | 5.3 | 0.0402 | 2019-04-22 |
CVE-2019-10247 | 3.5 | 5.3 | 0.0578 | 2019-04-22 |
CVE-2017-3211 | 3.5 | 5.3 | 0.0083 | 2020-01-15 |
CVE-2020-1652 | 3.5 | 5.6 | 0.0074 | 2020-07-17 |
CVE-2022-22541 | 3.5 | 6.5 | 0.0076 | 2022-04-12 |
CVE-2022-33692 | 3.5 | 4.0 | 0.0009 | 2022-07-12 |
CVE-2022-33694 | 3.5 | 4.0 | 0.0009 | 2022-07-12 |
CVE-2022-33696 | 3.5 | 4.0 | 0.0009 | 2022-07-12 |
CVE-2022-39848 | 3.5 | 4.0 | 0.0008 | 2022-10-07 |
CVE-2023-27465 | 3.5 | 4.6 | 0.0028 | 2023-06-13 |
CVE-2023-36919 | 3.5 | 5.3 | 0.0040 | 2023-07-11 |
CVE-2023-40570 | 3.5 | 5.3 | 0.0046 | 2023-08-25 |
CVE-2024-7267 | 3.5 | 6.5 | 0.0060 | 2024-08-07 |
CVE-2024-44121 | 3.5 | 4.3 | 0.0029 | 2024-09-10 |
CVE-2023-3441 | 3.5 | 6.6 | 0.0055 | 2024-10-01 |
CVE-2024-49354 | 3.5 | 5.3 | 0.0032 | 2025-01-18 |
CVE-2025-24316 | 3.5 | 5.3 | 0.0029 | 2025-02-28 |
CVE-2025-32791 UPD | 3.5 | 4.3 | 0.0023 | 2025-04-16 |
CVE-2025-4976 UPD | 3.5 | 4.3 | 0.0039 | 2025-07-24 |
CVE-2025-54831 | 3.5 | 6.5 | 0.0090 | 2025-09-26 |
CVE-2022-28794 | 1.5 | 2.2 | 0.0008 | 2022-06-07 |