MEDIUM 6.1

CVE-2026-11878: OpenText Access Manager XSS Vulnerability (5.1-5.1.2)

OpenText Access Manager versions 5.1 through 5.1.2 contain a cross-site scripting (XSS) vulnerability in web page generation. An attacker can inject malicious JavaScript code that executes in the browsers of users accessing the affected system. The vulnerability requires user interaction (such as clicking a crafted link) but does not require authentication, making it accessible to unauthenticated threat actors. While not currently listed in CISA's Known Exploited Vulnerabilities catalog, the combination of network accessibility and user-triggered execution means organizations should prioritize remediation.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.1 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weaknesses (CWE)
CWE-79
Affected products
3 configuration(s)
Published / Modified
2026-06-24 / 2026-06-29

NVD description (verbatim)

Improper 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.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

This is a reflected or stored XSS vulnerability (CWE-79) stemming from improper input validation during HTML/web page generation within OpenText Access Manager. The flaw allows an attacker to bypass input sanitization controls and inject arbitrary JavaScript that will be rendered and executed in the context of a user's browser session. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) indicates network-accessible attack surface, low complexity, no privilege requirement, required user interaction, and potential for scope change with limited confidentiality and integrity impact. The vulnerability affects versions 5.1 through 5.1.2 of Access Manager, suggesting that earlier or later versions may be unaffected or patched.

Business impact

Successful exploitation could allow attackers to steal session cookies, harvest credentials, redirect users to malicious sites, or perform unauthorized actions on behalf of compromised users. Access Manager typically guards sensitive identity and access control functions, so compromise of user sessions could grant attackers the ability to impersonate legitimate users and access downstream applications and data. Organizations with single sign-on (SSO) deployments are at heightened risk, as a compromised Access Manager session may unlock multiple critical resources.

Affected systems

OpenText Access Manager versions 5.1, 5.1.1, and 5.1.2 are confirmed affected. Organizations running these versions in production should immediately inventory their deployments. Earlier versions (pre-5.1) and later releases (post-5.1.2) may have different risk profiles and should be verified against OpenText vendor advisories.

Exploitability

The vulnerability is exploitable without authentication or elevated privileges, reducing the barrier to attack initiation. However, successful exploitation requires user interaction—typically a victim must click a malicious link or visit an attacker-controlled page that references the vulnerable Access Manager endpoint. This user-interaction requirement moderates the risk somewhat, but phishing campaigns or social engineering can reliably achieve this precondition. No exploit code has been identified in public disclosure, and the vulnerability is not yet tracked in CISA's KEV catalog, but that status may change as awareness spreads.

Remediation

Organizations must upgrade Access Manager to a patched version beyond 5.1.2. Verify the specific patch version and upgrade pathway with OpenText's official security advisory. In the interim, implement network-level controls (WAF rules, reverse proxy filtering) to block or sanitize requests containing common XSS payloads, and educate users to avoid clicking suspicious links from untrusted sources. Additionally, enforce strong session management practices and consider implementing Content Security Policy (CSP) headers to mitigate XSS impact even if input validation fails.

Patch guidance

Contact OpenText directly or consult their security advisory for the recommended patch version for Access Manager. Given that 5.1.2 is the latest affected release, patches are likely available in a later 5.1.x or 5.2+ release. Verify patch applicability to your deployment configuration before applying, as large identity systems require careful change management. Test the patch in a non-production environment first to ensure compatibility with your SSO ecosystem and downstream integrations.

Detection guidance

Monitor Access Manager logs for requests containing common XSS patterns (e.g., <script>, javascript:, onerror=, onload=) in URL parameters or POST bodies directed at page-generation endpoints. Deploy a Web Application Firewall (WAF) with XSS detection rules in front of Access Manager. Additionally, monitor for unusual browser-based activity originating from Access Manager sessions, such as credential exfiltration attempts or unauthorized API calls to downstream applications. Endpoint Detection and Response (EDR) tools can help identify compromised user workstations attempting to exploit the vulnerability.

Why prioritize this

Although the CVSS score of 6.1 (MEDIUM) is moderate, the context elevates priority: Access Manager is a critical identity control point, meaning XSS compromise can cascade to multiple downstream systems. The lack of authentication requirements and ease of exploitation (once user interaction is achieved) make this a suitable candidate for early patching, especially in zero-trust or high-sensitivity environments. The absence of active exploitation (not yet in KEV) provides a window of opportunity to patch before mass exploitation emerges.

Risk score, explained

The CVSS 3.1 score of 6.1 reflects a network-accessible XSS vector with user-interaction dependency. The 'scope change' (S:C) element indicates that compromised user context can affect other security domains. While direct availability impact is nil (A:N), confidentiality and integrity impacts (C:L/I:L) are present. The medium severity reflects the balance between broad accessibility and the user-interaction requirement. In context of Access Manager's role as an identity gateway, this medium CVSS score understates true business risk and should not be the sole driver of patching priority.

Frequently asked questions

Which versions of OpenText Access Manager are affected?

Access Manager versions 5.1, 5.1.1, and 5.1.2 are confirmed affected. Verify your installed version in the Access Manager administrative console or deployment documentation. Organizations running versions outside this range should confirm patch status with OpenText.

Do we need authentication to exploit this vulnerability?

No. The vulnerability is exploitable without valid Access Manager credentials. An unauthenticated attacker can craft a malicious URL or web page and trick a user into clicking it. This lowers the barrier to attack compared to vulnerabilities requiring privileged access.

What is the risk if our Access Manager is behind a firewall?

Network segmentation reduces but does not eliminate risk. If Access Manager is accessible to internal users or if attackers gain network access (e.g., via phishing or lateral movement), the vulnerability remains exploitable. Additionally, if Access Manager is Internet-facing (common in cloud or hybrid deployments), the risk is significantly higher.

Is there a workaround if we cannot patch immediately?

Partial mitigation is possible: implement a Web Application Firewall to filter XSS payloads, enforce strong session management and re-authentication for sensitive operations, deploy Content Security Policy headers, and educate users to distrust unexpected links. However, these are temporary measures. Patching is the definitive remediation.

This analysis is provided for informational purposes and represents SEC.co's interpretation of publicly available vulnerability data as of the publication date. The CVSS score, affected version ranges, and patch status reflect the source advisory; however, specific patch version numbers and availability timelines should be verified directly with OpenText's official security bulletins and support channels. Organizations should conduct their own risk assessment accounting for their specific Access Manager deployment topology, exposure, and downstream dependencies. This document does not constitute professional security advice and should not replace engagement with qualified security engineers or the vendor's support team. Source: NVD (public-domain), retrieved 2026-07-30. Analysis generated by SEC.co (claude-haiku-4-5).