dbcve.org
Access ManagerApplication · Microfocus

CVE-2021-22528

MEDIUM · 5.4 CVSS v3.1 Published 2021-09-13
Fix available
A fix is available. Upgrade to 4.5.4 / 5.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Reflected Cross Site Scripting (XSS) vulnerability in NetIQ Access Manager prior to 5.0.1 and 4.5.4

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

Reflected Cross Site Scripting (XSS) vulnerability in NetIQ Access Manager allows attackers to inject malicious scripts through URL parameters that are reflected back to users without proper sanitization. This could enable session hijacking, credential theft, or defacement of web pages rendered by the vulnerable application.

MitigationApply vendor patches 5.0.1 or 4.5.4 as appropriate for the deployed version branch to address the XSS vulnerability. Until patched, implement URL parameter validation and output encoding at upstream proxies or WAF.

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:>= 4.5.0, < 4.5.4>= 5.0, < 5.0.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
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 checks

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

  1. Locate Access Manager version information
    Check the administration console or system information page for Access Manager, typically found under the product's 'About' or 'System Information' section in the NAM/NAM Admin console. The version is also often visible in the footer of the admin web interface or accessible via command line using 'namadmin -version' or similar version query tool provided with the installation.
    Affected if The installed version falls within 4.5.0 through 4.5.3, or 5.0.0 (the versions before the patches 4.5.4 and 5.0.1 respectively).
  2. Identify exposed web components
    Determine if the Access Manager web interface or any of its endpoints are accessible from network locations where untrusted users could trigger the reflected XSS. This includes the administration console, landing pages, or any URL-handling components that process user-supplied parameters.
    Affected if The administration console or any web-facing NAM component is exposed without being behind a filtering proxy that performs URL parameter validation.
  3. Review proxy or WAF configuration
    Inspect any upstream proxy, reverse proxy, or Web Application Firewall (WAF) positioned in front of Access Manager. Verify whether URL parameter validation or output encoding rules are actively enforced for requests destined for NAM.
    Affected if No input validation or output encoding is configured at the proxy/WAF layer, and the vulnerable version of Access Manager is in use.

A user is affected if their installed Access Manager version is between 4.5.0 and 4.5.3 inclusive, or is exactly 5.0.0, and the web interface is exposed without protective filtering.

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 4.5.4 / 5.0.1 or later
Fixed in 4.5.45.0.1
Interim mitigation

Apply vendor patches 5.0.1 or 4.5.4 as appropriate for the deployed version branch to address the XSS vulnerability. Until patched, implement URL parameter validation and output encoding at upstream proxies or WAF.

Recommended fix High confidence

Access Manager 4.5.4 (for 4.5.x line) or Access Manager 5.0.1 (for 5.0.x line)

  1. Determine your current Access Manager version by checking the administration console or system information
  2. For Access Manager 4.5.x: Plan upgrade path to version 4.5.4
  3. For Access Manager 5.0.x: Plan upgrade path to version 5.0.1
  4. Back up the current Access Manager configuration and all related data
  5. Review Micro Focus support documentation for upgrade prerequisites and requirements
  6. Perform the upgrade to the target fixed version (4.5.4 or 5.0.1) following official upgrade documentation
  7. After upgrade, verify the Access Manager components are functioning correctly
  8. Confirm the XSS vulnerability is resolved by testing the affected parameters
Caveat Review Micro Focus release notes for 4.5.4 and 5.0.1 for any compatibility or configuration changes before upgrading

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
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22528 — 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-2021-22528 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