Skip to main content
CVE-2025-33110VulnerabilityPublished

CVE-2025-33110: IBM OpenPages · Basic XSS

Affects IBM OpenPagesSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
IBM OpenPagesAffected
  • =9.1
  • =9.0
Fixed in–

AI-suggested

1. Implement strict input validation and sanitization on all user-supplied data fields within IBM OpenPages to prevent injection of malicious HTML or script content. 2. Apply comprehensive output encoding (e.g., HTML entity encoding) before rendering user inputs in web pages to neutralize potentially harmful tags. 3. Enforce Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 4. Limit user privileges to the minimum necessary to reduce the risk posed by authenticated attackers. 5. Monitor application logs and user activity for unusual behavior indicative of exploitation attempts. 6. Educate users about phishing and social engineering risks that could facilitate exploitation requiring user interaction. 7. Engage with IBM support to track patch releases and apply updates promptly once available. 8. Consider deploying web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting OpenPages. 9. Conduct regular security assessments and penetration testing focused on input validation and XSS vulnerabilities within the OpenPages environment.

Description

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.

References

Community reviews

Loading reviews…