CVE-2025-33014
Ibm Sterling B2B Integrator 6.0.0.0 – 6.1.2.7_1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NSummary
CVE-2025-33014 is a medium-severity Use of Web Link to Untrusted Target with window.opener Access (CWE-1022) vulnerability in Ibm Sterling B2B Integrator. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 11th 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-21923
Vulnerability Data
IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7 and 6.2.0.0 through 6.2.0.4 uses a web link with untrusted references to an external site. A remote attacker could exploit this vulnerability to expose sensitive information or perform…
more
unauthorized actions on the victims’ web browser.
- 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.