CVE-2022-26951
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 · uneditedArcher 6.x through 6.10 (6.10.0.0) contains a reflected XSS vulnerability. A remote SAML-unauthenticated malicious Archer user could potentially exploit this vulnerability by tricking a victim application user into supplying malicious HTML or JavaScript code to the vulnerable web application; the malicious code is then reflected back to the victim and gets executed by the web browser in the context of the vulnerable web application.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in RSA Archer versions 6.x through 6.10. An unauthenticated remote attacker can craft malicious HTML or JavaScript code and trick a victim user into submitting it to the vulnerable web application; the payload is then reflected back to the victim and executed in their browser within the context of the Archer application.
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>= 6.1.0.0, < 6.10.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify RSA Archer installed versionLog into the RSA Archer web interface as an administrator and navigate to the About or System Information page, typically found under Administration > System > About. Alternatively, check the installation directory for version metadata files or review the installer logs from the initial deployment.Affected if The installed version falls within 6.1.0.0 through 6.10.0.0 (inclusive), meaning it is lower than 6.10.0.1.
-
Confirm web application is internet-facingDetermine if the RSA Archer web interface is accessible from untrusted networks by reviewing network firewall rules, load balancer configurations, or DMZ settings. Attempt to access the Archer login page from an external network or review reverse proxy/access logs.Affected if The Archer web application is directly exposed to the internet or untrusted networks without a WAF filtering layer.
-
Identify SAML or external authentication configurationReview the RSA Archer administration console for configured SAML Identity Providers or external authentication methods under Administration > Access Control > Authentication Methods. Note which authentication workflows are actively enabled.Affected if SAML authentication or any external authentication method is enabled and used for user login, as the XSS vulnerability exists within these authentication flows.
You are affected if your RSA Archer version is 6.1.0.0 through 6.10.0.0 and the web application with SAML or external authentication is exposed to users or untrusted networks.
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 · scoped6.10.0.1
Apply vendor-provided patches for CVE-2022-26951. As a temporary control, deploy a Web Application Firewall (WAF) to filter malicious requests. Implement robust input validation and output encoding for all user-supplied data in SAML and other authentication flows.
6.10.0.1 or later
- Verify current Archer installation version via the Administration > System > Settings > General page
- Review Archer 6.10.0.1 release notes for any prerequisites or known issues
- Create a full backup of the Archer database and application files
- Schedule a maintenance window for the upgrade
- Download Archer version 6.10.0.1 or later from the RSA Archer Suite download portal
- Follow the standard Archer upgrade procedure: stop IIS services, run the installer, verify database migration completes, restart services
- Validate the upgrade was successful by logging into the Archer UI and checking the System Administration page shows version 6.10.0.1 or higher
- Test critical workflows to ensure functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26951 — 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-26951 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