CVE-2025-42941
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:NSummary
CVE-2025-42941 is a low-severity Use of Web Link to Untrusted Target with window.opener Access (CWE-1022) vulnerability in Sap (inferred from references). Its CVSS base score is 3.5 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-24213
Vulnerability Data
SAP Fiori (Launchpad) is vulnerable to Reverse Tabnabbing vulnerability due to inadequate external navigation protections for its link (<a>) elements. An attacker with administrative user privileges could exploit this by leveraging compromised or malicious pages. While administrative access is necessary…
more
for certain configurations, the attacker does not need the administrative privileges to execute the attack. This could result in unintended manipulation of user sessions or exposure of sensitive information. The issue impacts the confidentiality and integrity of the system, but the availability remains unaffected.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.4.8
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.
Secure SDLC practices directly require mitigations such as rel="noopener" on external links.
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.
Security testing can detect missing protections on external links through automated or manual checks.
Web filtering can block or warn on links to untrusted external domains, reducing the attack surface for window.opener abuse.
Secure development lifecycle processes require design and code reviews that should identify missing rel="noopener" or target="_blank" mitigations.
Application security requirements can mandate explicit handling of external links and window.opener protections.
Secure architecture principles include isolation of untrusted content and safe navigation patterns that mitigate opener-based attacks.
Secure coding standards directly require the use of rel="noopener noreferrer" on external links, eliminating the weakness.