CVE-2026-11708
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 WebSphere Application Server 9.0, and 8.5 is affected by a cross-site scripting vulnerability in the administrative console's integrated help system.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 WebSphere Application Server versions 9.0 and 8.5 contain a cross-site scripting vulnerability in the administrative console's integrated help system. The vulnerability allows attackers to inject malicious scripts through the help system interface, potentially compromising administrator sessions given the CRITICAL CVSS score of 9.3.
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>= 8.5.0.0, < 8.5.5.31>= 9.0.0.0, < 9.0.5.29CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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.
-
Identify WebSphere Application Server versionUse the versionInfo command (versionInfo.sh or versionInfo.bat) from the bin directory, or check the install_root/properties/version.properties file. Alternatively, log into the admin console and navigate to Troubleshooting > Version Information.Affected if The installed version falls within >= 8.5.0.0 and < 8.5.5.31, or >= 9.0.0.0 and < 9.0.5.29
-
Confirm admin console is accessibleVerify the administrative console is running and reachable by accessing the console URL (typically https://hostname:9043/ibm/console or http://hostname:9060/ibm/console). Check if the console is enabled in the deployment manager or standalone server configuration.Affected if The administrative console is enabled and accessible over the network
-
Verify integrated help system is enabledIn the admin console, navigate to System Administration > Console Settings and check if the integrated help system is enabled. Alternatively, check the was.cell.deployedResources.xml or ibm-webconsole.xml configuration files for help system settings.Affected if The integrated help system feature is enabled in the console configuration
-
Check console security configurationReview the administrative console security settings under Security > Global Security to determine if the console is using proper authentication. Also check if the help system accepts user-supplied input through URL parameters or search fields.Affected if The help system interface is exposed without proper input sanitization controls or the console is accessible to untrusted users
A user is affected if their WebSphere Application Server version is 8.5.0.0 through 8.5.5.30 or 9.0.0.0 through 9.0.5.28 AND the administrative console with the integrated help system is enabled and accessible.
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 · scoped8.5.5.319.0.5.29
Apply the latest IBM WebSphere fix pack or interim fix that addresses this XSS vulnerability in the admin console help system. Consider restricting access to the administrative console to trusted networks as an interim control.
8.5.5.31 for 8.5.x branches; 9.0.5.29 for 9.0.x branches
- 1. Review IBM WebSphere Application Server upgrade documentation for your current version
- 2. Backup your current WebSphere configuration and application data
- 3. Download IBM WebSphere Application Server fix pack 8.5.5.31 (for 8.5.x versions) or 9.0.5.29 (for 9.0.x versions) from IBM Fix Central
- 4. Stop all WebSphere Application Server processes before applying the update
- 5. Install the appropriate fix pack using the IBM Installation Manager or Update Installer
- 6. Verify the installation completed successfully
- 7. Start WebSphere Application Server and confirm all applications are functioning properly
- 8. Log in to the administrative console and verify the integrated help system loads without XSS vulnerabilities
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11708 — 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-2026-11708 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