Security Resilience

CWE · MITRE source

CWE-830Inclusion of Web Functionality from an Untrusted Source

Abstraction: Variant · CVEs in our corpus: 13

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: 14 October 2026 20:41 UTC

OWASP Top 10 for Web (2025)

This weakness contributes to A08:2025 Software or Data Integrity Failures.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • SC-18 Mobile Code
  • SC-35 External Malicious Code Identification
  • GV.SC-05
  • GV.SC-06
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (2)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
SC-18Mobile CodeSCgraded mostly Restricting mobile code technologies and monitoring their use blocks web functionality (e.g., scripts) loaded from untrusted sources.
SC-35External Malicious Code IdentificationSCComponents that flag malicious websites reduce the ability to pull and render web functionality from untrusted external sources.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2024-29944 6.98.40.04702024-03-22
CVE-2023-2588 6.88.80.01122023-05-22
CVE-2025-64496 6.47.30.07232025-11-08
CVE-2024-42381 6.08.30.00652024-07-31
CVE-2025-61478 5.77.50.00262026-08-26
CVE-2021-28162 4.86.10.00782021-03-12
CVE-2025-33028 4.76.10.00512025-04-15
CVE-2024-35180 4.56.10.00292024-05-21
CVE-2025-33026 4.56.10.00292025-04-15
CVE-2025-33027 4.56.10.00292025-04-15
CVE-2025-43703 4.56.10.00232025-04-16
CVE-2025-46652 4.56.10.00322025-04-26