Prime Access RegistrarApplication · Cisco
CVE-2022-20626
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 · uneditedA vulnerability in the web-based management interface of Cisco Prime Access Registrar Appliance could allow an authenticated, remote attacker to conduct a cross-site scripting attack against a user of the interface. The attacker would require valid credentials for the device. This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or access sensitive, browser-based information.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in the web-based management interface of Cisco Prime Access Registrar Appliance. The interface fails to properly validate user-supplied input, allowing an authenticated attacker to inject malicious script code via crafted URLs. When other users click these links or access the affected interface, the attacker's script executes in their browser context, enabling session hijacking or data theft.
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
Prime Access RegistrarApplication
< 9.2.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco Prime Access Registrar is installedIdentify if Cisco Prime Access Registrar Appliance is deployed in your environment by reviewing your inventory systems, network diagrams, or by logging into the appliance.Affected if The product is present in your environment
-
Check installed version numberAccess the appliance via CLI or web management interface and retrieve the version number. In the CLI, this is typically done with a 'show version' or 'show installed' type command. In the web interface, check the About or Dashboard page.Affected if The installed version is lower than 9.2.1 (for example, 9.2.0, 9.1.x, or earlier releases)
-
Verify web-based management interface is enabledCheck if the web-based management interface (HTTP/HTTPS) is currently enabled and accessible on the appliance. This can be confirmed by attempting to reach the management interface URL or by reviewing interface configuration settings.Affected if The web management interface is enabled and reachable
You are affected if Cisco Prime Access Registrar is installed with a version lower than 9.2.1 and the web-based management interface is enabled.
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.
dbcve · scoped9.2.1
Apply the Cisco software update for CVE-2022-20626 as soon as possible in a staged manner (dev/staging before production), and verify the XSS payload is no longer executable in the management interface.
9.2.1
- Obtain Cisco Prime Access Registrar version 9.2.1 or later from the Cisco software download center
- Verify the current installed version by accessing the web-based management interface or checking the system
- Follow Cisco's standard upgrade procedure for Prime Access Registrar Appliance, typically involving backing up the current configuration
- Upload and install the 9.2.1 or later version through the Appliance Administrator interface
- After upgrade, verify the new version is running and confirm the vulnerability is resolved by logging into the web interface
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prime Access Registrar
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20626 — 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-2022-20626 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