CWE · MITRE source
CWE-942Permissive Cross-domain Security Policy with Untrusted Domains
The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
If a cross-domain policy file includes domains that should not be trusted, such as when using wildcards under a high-level domain, then the application could be attacked by these untrusted domains. In many cases, the attack can be launched without the victim even being aware of it.
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: full · 6 mapping(s) from 3 framework(s): ATT&CK 3 (partial) · ASVS 5.0 2 (mostly) · OWASP-Web 1 (full)
OWASP Top 10 for Web (2025)
This weakness contributes to A02:2025 Security Misconfiguration.
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-2022-31736 | 7.0 | 9.8 | 0.0106 | 2022-12-22 |
CVE-2022-26969 | 7.0 | 9.8 | 0.0093 | 2022-12-26 |
CVE-2024-25124 UPD | 7.0 | 9.4 | 0.0066 | 2024-02-21 |
CVE-2026-1181 | 7.0 | 9.0 | 0.0031 | 2026-01-19 |
CVE-2026-28792 | 7.0 | 9.6 | 0.0053 | 2026-03-12 |
CVE-2026-30924 | 7.0 | 9.6 | 0.0026 | 2026-03-19 |
CVE-2026-34449 | 7.0 | 9.6 | 0.0050 | 2026-03-31 |
CVE-2026-8948 UPD | 7.0 | 9.1 | 0.0042 | 2026-05-19 |
CVE-2026-22812 | 6.0 | 8.8 | 0.1696 | 2026-01-12 |
CVE-2021-34435 | 5.5 | 8.8 | 0.0060 | 2021-09-01 |
CVE-2022-47717 | 5.5 | 7.5 | 0.0073 | 2023-02-01 |
CVE-2023-23464 | 5.5 | 8.1 | 0.0048 | 2023-02-15 |
CVE-2023-2360 | 5.5 | 7.5 | 0.0039 | 2023-04-28 |
CVE-2023-46098 | 5.5 | 8.0 | 0.0062 | 2023-11-14 |
CVE-2023-46281 | 5.5 | 7.1 | 0.0094 | 2023-12-12 |
CVE-2023-38122 | 5.5 | 7.2 | 0.0148 | 2024-05-03 |
CVE-2023-38125 | 5.5 | 8.8 | 0.0106 | 2024-05-03 |
CVE-2024-37131 | 5.5 | 7.5 | 0.0049 | 2024-06-13 |
CVE-2024-41659 | 5.5 | 8.1 | 0.0061 | 2024-08-20 |
CVE-2024-41657 | 5.5 | 8.1 | 0.0075 | 2024-08-20 |
CVE-2024-11071 | 5.5 | 8.8 | 0.0018 | 2025-04-07 |
CVE-2025-25234 UPD | 5.5 | 7.1 | 0.0024 | 2025-04-17 |
CVE-2025-43480 | 5.5 | 8.1 | 0.0045 | 2025-11-04 |
CVE-2025-13017 | 5.5 | 8.1 | 0.0022 | 2025-11-11 |
CVE-2025-13019 | 5.5 | 8.1 | 0.0022 | 2025-11-11 |