CVE-2025-46652
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NSummary
CVE-2025-46652 is a medium-severity Inclusion of Web Functionality from an Untrusted Source (CWE-830) vulnerability in Izarc (inferred from references). Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-18 (Mobile Code) and CM-7 (Least Functionality) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12481
Vulnerability Data
In IZArc through 4.5, there is a Mark-of-the-Web Bypass Vulnerability. When a user performs an extraction from an archive file that bears Mark-of-the-Web, Mark-of-the-Web is not propagated to the extracted files. NOTE: this is disputed because Mark-of-the-Web propagation can increase…
more
risk via security-warning habituation, and because the intended control sphere for file-origin metadata (e.g., HostUrl in Zone.Identifier) may be narrower than that for reading the file's content.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Defines acceptable mobile/active code and authorizes/monitors its use, directly blocking inclusion of untrusted web scripts or widgets.
Configures the system to permit only essential functionality, thereby restricting the ability to embed arbitrary external web code.
Requires external service providers to meet the organization's security and privacy requirements before their functionality (e.g., widgets) may be integrated.
Establishes processes to identify and remediate supply-chain weaknesses that would allow untrusted external web components to be incorporated.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Contractual requirements can mandate vetting of web sources and prohibit untrusted inclusions.
Due diligence before supplier relationships directly prevents inclusion of untrusted web functionality.
Assessing supplier risks and products reduces the chance of embedding untrusted web widgets or scripts.
Supplier assessments prior to acquisition address the root risk of untrusted web sources.
Integrity checks on acquired software can catch untrusted web functionality before use.
Secure SDLC practices can include policies forbidding inclusion of untrusted external web code.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure architecture principles discourage embedding untrusted content, yet require additional controls for full mitigation.
Security testing can detect the weakness, but does not prevent its introduction during design or coding.
Network security controls can restrict or block untrusted external web content, but do not specifically address inclusion of web widgets.
Web filtering can prevent loading of untrusted web functionality, directly mitigating the weakness.
Application security requirements can mandate vetting of external web components, but do not guarantee technical enforcement.
Secure coding practices can avoid unsafe inclusion of external scripts, but coverage depends on developer adherence.