CWE · MITRE source
CWE-830Inclusion of Web Functionality from an Untrusted Source
The product includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the product, potentially granting total access and control of the product to the untrusted source.
Including third party functionality in a web-based environment is risky, especially if the source of the functionality is untrusted. Even if the third party is a trusted source, the product may still be exposed to attacks and malicious behavior if that trusted source is compromised, or if the code is modified in transmission from the third party to the product. This weakness is common in "mashup" development on the web, which may include source functionality from other domains. For example, Javascript-based web widgets may be inserted by using '<SCRIPT SRC="http://other.domain.here">' tags, which causes the code to run in the domain of the product, not the remote site from which the widget was loaded. As a result, the included code has access to the local DOM, including cookies and other data that the developer might not want the remote site to be able to access. Such dependencies may be desirable, or even required, but sometimes programmers are not aware that a dependency exists.
Last updated: 04 July 2026 13:15 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 · 3 mapping(s) from 2 framework(s): ATT&CK 2 (partial) · OWASP-Web 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A08:2025 Software or Data Integrity Failures.
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-18 | Mobile Code | SC | Restricting mobile code technologies and monitoring their use blocks web functionality (e.g., scripts) loaded from untrusted sources. |
SC-35 | External Malicious Code Identification | SC | Components that flag malicious websites reduce the ability to pull and render web functionality from untrusted external sources. |
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-2023-2588 | 5.5 | 8.8 | 0.0112 | 2023-05-22 |
CVE-2024-29944 UPD | 5.5 | 8.4 | 0.0470 | 2024-03-22 |
CVE-2024-42381 | 5.5 | 8.3 | 0.0061 | 2024-07-31 |
CVE-2025-64496 | 5.5 | 7.3 | 0.0777 | 2025-11-08 |
CVE-2021-28162 | 3.5 | 6.1 | 0.0078 | 2021-03-12 |
CVE-2024-35180 | 3.5 | 6.1 | 0.0029 | 2024-05-21 |
CVE-2025-33026 | 3.5 | 6.1 | 0.0023 | 2025-04-15 |
CVE-2025-33027 | 3.5 | 6.1 | 0.0023 | 2025-04-15 |
CVE-2025-33028 | 3.5 | 6.1 | 0.0048 | 2025-04-15 |
CVE-2025-43703 UPD | 3.5 | 6.1 | 0.0019 | 2025-04-16 |
CVE-2025-46652 UPD | 3.5 | 6.1 | 0.0027 | 2025-04-26 |