Cyber Resilience

CVE-2025-36223

Ibm Openpages 9.0.0 … 9.1.0

Published
12 November 2025
Modified
18 November 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0016 6th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-36223 is a medium-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Ibm Openpages. Its CVSS base score is 5.4 (Medium).

Operationally, ranked at the 6th 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 AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM OpenPages 9.0 and 9.1 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or…

more

session hijacking.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-36121Same product: Ibm Openpages
CVE-2025-2670Same product: Ibm Openpages
CVE-2025-36082Same product: Ibm Openpages
CVE-2025-33110Same product: Ibm Openpages
CVE-2025-27368Same product: Ibm Openpages
CVE-2024-40686Same vendor: Ibm
CVE-2025-27901Same vendor: Ibm
CVE-2025-66485Same vendor: Ibm
CVE-2025-2950Same vendor: Ibm
CVE-2024-51451Same vendor: Ibm

Affected Assets

ibm
openpages
9.0.0, 9.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SC-7 Boundary Protection
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.2.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation of all input (including HOST headers) to block the header-injection flaw described in the CVE.

prevent

Boundary-protection mechanisms (e.g., WAF rules) can inspect and sanitize HOST headers before they reach OpenPages.

prevent

Enforces information-flow rules that can reject or sanitize untrusted header values used for XSS or session hijacking.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.

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.

detects

Security testing catches header-injection issues before release, covering most of the weakness.

prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.

prevents

Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.

prevents

Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.

References