Clearpass Policy ManagerApplication · Arubanetworks

CVE-2021-26682

MEDIUM · 6.1 CVSS v3.1 Published 2021-02-23
Fix available
A fix is available. Upgrade to 6.7.14 / 6.8.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A remote reflected cross-site scripting (XSS) vulnerability was discovered in Aruba ClearPass Policy Manager version(s): Prior to 6.9.5, 6.8.8-HF1, 6.7.14-HF1. A vulnerability in the guest portal interface of ClearPass could allow a remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the portal. A successful exploit could allow an attacker to execute arbitrary script code in a victim’s browser in the context of the guest portal interface.

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 · high confidence

A remote reflected cross-site scripting (XSS) vulnerability exists in the guest portal interface of Aruba ClearPass Policy Manager. Attackers can craft malicious URLs containing script code that gets reflected back and executed in victims' browsers when they interact with the crafted link, allowing session hijacking or actions performed in the context of the portal.

MitigationUpgrade ClearPass Policy Manager to version 6.9.5, 6.8.8-HF1, or 6.7.14-HF1 (or later) to remediate the reflected XSS vulnerability in the guest portal.

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
Clearpass Policy ManagerApplication
Affected:< 6.7.14>= 6.8.0, < 6.8.8>= 6.9.0, < 6.9.5= 6.7.14= 6.8.8

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
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 checks

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

  1. Identify installed ClearPass Policy Manager version
    Log into the ClearPass admin web interface and navigate to Administration > About, or run the CLI command 'show version' to retrieve the exact version number
    Affected if The installed version is less than 6.7.14, or is 6.8.0 through 6.8.7, or is 6.9.0 through 6.9.4, or is exactly 6.7.14 (unpatched)
  2. Confirm guest portal is accessible
    Attempt to access the guest portal URL (typically https://<clearpass-host>/guest) using a web browser or curl. Check if the page loads and presents a login or registration form
    Affected if The guest portal interface responds with a login or registration page, indicating the feature is enabled and exposed
  3. Verify the guest portal endpoint reflects user input
    Craft a test URL such as https://<clearpass-host>/guest?test=<script>alert(1)</script> and observe if the script tags appear unescaped in the page source or trigger an alert
    Affected if The URL parameter value is reflected verbatim in the HTML response without proper encoding, confirming the XSS condition exists

The environment is affected if ClearPass Policy Manager version is unpatched (below 6.7.14-HF1/6.8.8-HF1 or below 6.9.5) AND the guest portal interface is accessible and reflects URL parameters unsanitized.

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.

From vendor data
Upgrade available Upgrade to 6.7.14 / 6.8.8 / 6.9.5 or later
Fixed in 6.7.146.8.86.9.5
Interim mitigation

Upgrade ClearPass Policy Manager to version 6.9.5, 6.8.8-HF1, or 6.7.14-HF1 (or later) to remediate the reflected XSS vulnerability in the guest portal.

Fix this in Clearpass Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-26682 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