CVE-2026-11878
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 · uneditedImproper neutralization of input during web page generation ('cross-site scripting') vulnerability in OpenText Access Manager allows Cross-Site Scripting (XSS). This issue affects Access Manager: from 5.1 through 5.1.2.
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 confidenceOpenText Access Manager versions 5.1 through 5.1.2 contain a cross-site scripting (XSS) vulnerability where user-supplied input is not properly neutralized before being rendered in web pages. This allows authenticated attackers to inject malicious scripts that execute in the context of other users' sessions.
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>= 5.0, < 5.1= 5.1CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Access Manager versionLocate the installed version of OpenText Access Manager or Microfocus Access Manager. This is typically found in the product's admin console, about page, or via command line tools such as 'nkmfrpt' or by checking the installation directory for version files.Affected if The installed version is 5.1, 5.1.1, or 5.1.2 (within the 5.1 through 5.1.2 range) or falls within >= 5.0 and < 5.1 per Microfocus listing.
-
Confirm web interface is enabledAccess the Access Manager admin console or web portal. Verify the web-based management interface is accessible and not disabled.Affected if The web interface is active and reachable, as XSS executes through rendered web pages.
-
Verify authentication is configuredCheck whether user authentication is enabled for the Access Manager web portal. Review the authentication methods configured in the Identity Server or Authentication section.Affected if User authentication is enabled, as the CVE requires authenticated attackers to inject malicious scripts.
-
Inspect web logs for XSS patternsReview Access Manager logs (typically stored in the 'logs' or 'diagnostics' directory) for any unusual script tags, JavaScript event handlers, or encoded XSS payloads in user input fields.Affected if Unusual XSS payload patterns appear in the logs, indicating possible exploitation attempts.
-
Check input sanitization configurationExamine the Access Manager configuration files and admin settings for input validation or sanitization rules applied to web page rendering. Look for XSS protection settings in the policy or endpoint configuration.Affected if Input sanitization is missing or disabled for web page outputs, allowing unsanitized user input to be rendered.
A user is affected if their Access Manager version is within 5.1 through 5.1.2 and the web interface with authentication is enabled, allowing unsanitized user input to be rendered in web pages.
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.
From vendor data5.1
Apply the vendor-supplied patch from OpenText for Access Manager. Until the patch is available, implement WAF rules to filter XSS payloads and sanitize user inputs in affected endpoints.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11878 — 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-11878 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