CVE-2025-33110
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM OpenPages 9.1 and 9.0 with Watson contains an HTML injection vulnerability allowing remote attackers to inject malicious HTML code into web pages. When victims view the injected content, the HTML executes within the security context of the hosting site, potentially enabling cross-site scripting, session hijacking, or phishing attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9.0.0= 9.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check IBM OpenPages versionAccess the IBM OpenPages admin console or check the installed software version using the product's built-in version information (typically available in About or System Information section of the admin interface)Affected if The installed version is exactly 9.0.0 or exactly 9.1.0
-
Verify web interface is enabledConfirm that the IBM OpenPages web application is accessible by accessing the main URL (typically /op upon installation) in a browserAffected if The web interface is exposed and accessible to users or attackers
-
Identify user input points in web applicationNavigate through the IBM OpenPages web interface and identify fields or parameters that accept user-supplied content (such as report names, descriptions, comments, or custom fields)Affected if User-accessible input fields exist that process and display content without proper sanitization
You are affected if you are running exactly IBM OpenPages version 9.0.0 or 9.1.0 and have the web interface accessible with user input fields that accept and display HTML content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement strict input validation and output encoding for all user-supplied data, and configure Content Security Policy headers to restrict inline script execution.
Obtain the fixed version or iFix from IBM Security Bulletin (refer to ibm.com for exact version)
- Consult the official IBM Security Bulletin for CVE-2025-33110 at ibm.com to obtain the specific patch or fixed version number
- Apply the IBM interim fix (iFix) or upgrade to the fixed release as specified in the IBM advisory
- Verify the fix by testing that HTML injection attempts are properly sanitized or blocked
- Confirm the remediation by reviewing IBM's published solution for this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33110 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33110 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data