dbcve.org
Access ManagerApplication · Microfocus

CVE-2026-11877

HIGH · 7.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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 · unedited
An unauthorized user can modify configuration through API calls that affects the OpenText Access Manager. This issue affects Access Manager before 5.1.3.

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 confidence

OpenText Access Manager before version 5.1.3 contains an authentication/authorization flaw that allows unauthenticated users to modify system configuration via API calls, potentially leading to unauthorized changes to the security appliance's settings.

MitigationUpgrade OpenText Access Manager to version 5.1.3 or later to remediate this vulnerability.

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
Access ManagerApplication
Affected:>= 5.0, < 5.1= 5.1

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Access Manager version
    Locate the installed version of OpenText Access Manager or Microfocus Access Manager through the administration console, product documentation, or system inventory. Common locations include the About section in the admin UI or the product's version file in the installation directory.
    Affected if The installed version is 5.0.x, 5.1.0, 5.1.1, or 5.1.2 (any version >= 5.0 but < 5.1.3)
  2. Verify API accessibility
    Determine if the Access Manager administrative API endpoints are network-accessible from untrusted networks. Check firewall rules, reverse proxy configurations, or access control lists that govern who can reach the API ports.
    Affected if The administrative API is reachable from networks where untrusted users could send requests
  3. Check API authentication configuration
    Review the Access Manager configuration settings related to API authentication and authorization. Look for settings that control whether API endpoints require valid credentials before accepting configuration changes.
    Affected if API endpoints allow configuration modifications without requiring authentication tokens or session credentials
  4. Test API endpoint behavior
    If you have authorization, send a test API request to a configuration endpoint without providing credentials to observe whether the request is accepted or rejected.
    Affected if The API accepts and processes configuration change requests without returning an authentication error

You are affected if your Access Manager version is 5.0.x or any 5.1.x version before 5.1.3 AND the administrative API is accessible from your network without requiring authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.1 or later
Fixed in 5.1
Interim mitigation

Upgrade OpenText Access Manager to version 5.1.3 or later to remediate this vulnerability.

Recommended fix High confidence

Access Manager 5.1.3 or later

  1. 1. Back up the current Access Manager configuration and database
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Download Access Manager version 5.1.3 or later from the OpenText portal (portal.microfocus.com or portal.opentext.com)
  4. 4. Follow the official upgrade documentation to install the new version
  5. 5. Verify that the API access controls are properly configured after upgrade
  6. 6. Test that unauthorized users can no longer modify configuration through API calls
  7. 7. Monitor logs for any unauthorized configuration change attempts
Caveat Review release notes for any breaking changes between 5.0.x/5.1 and 5.1.3; some API endpoints or configuration formats may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11877 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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