Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NSummary
CVE-2025-33110 is a medium-severity Basic XSS (CWE-80) vulnerability in Ibm Openpages. Its CVSS base score is 5.4 (Medium).
Operationally, ranked at the 9th 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 SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-38161
Vulnerability Data
IBM OpenPages 9.1, and 9.0 with Watson is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly blocks the HTML injection at input by validating and rejecting untrusted markup before it is stored or reflected in IBM OpenPages pages.
Requires output filtering/encoding of all dynamic content so that injected HTML cannot execute in the victim's browser context.
Enforces information-flow rules that can prevent untrusted user-supplied data from reaching browser-rendered pages without sanitization.
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 output encoding and input validation that prevent basic XSS.
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 in development catches unneutralized script tags before release.
Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.
Application security requirements explicitly call for neutralization of script-related HTML tags.
Secure coding standards require proper escaping of <, >, & to block XSS.
Web filtering can block some reflected XSS payloads at the network edge.