CVE-2022-26947
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.9 SP3 (6.9.3.0) contains a reflected XSS vulnerability. A remote authenticated 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 · high confidenceRSA Archer 6.x through 6.9 SP3 (6.9.3.0) contains a reflected cross-site scripting (XSS) vulnerability. A remote authenticated malicious user can trick a victim application user into submitting malicious HTML or JavaScript code, which gets reflected back to the victim and executed in their browser within the context of the vulnerable web 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.9.3.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.
-
Identify RSA Archer versionAccess the Archer UI and navigate to Help > About, or check the version file in the installation directory. The version format is typically 6.x.x.x.Affected if The installed version is 6.1.0.0 or higher but lower than 6.9.3.1
-
Confirm the build numberLocate the build or sub-version in the Archer About page or installation metadata. Versions like 6.9.0.0 through 6.9.3.0 are in the affected range.Affected if The build number is 6.9.3.0 or earlier (below 6.9.3.1)
-
Verify web application accessibilityConfirm the RSA Archer web interface is running and accessible to users. The vulnerability is exploitable through the web application.Affected if The web application is accessible to authenticated users
-
Check patch statusReview installed patches through the Archer Control Panel or consult vendor documentation for patch level. The fixed version is 6.9.3.1.Affected if The CVE-2022-26947 patch has not been applied and the version remains in the vulnerable range
A system is affected if it runs RSA Archer version 6.1.0.0 through 6.9.3.0 with the web interface enabled and the vendor patch not applied.
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.9.3.1
Apply the vendor patch for CVE-2022-26947. Additionally, implement robust input validation and output encoding on all user-supplied input fields to prevent XSS attacks.
Archer 6.9.3.1 or later
- Review Archer 6.9.3.1 release notes and upgrade prerequisites on the Archer IRM community portal
- Create a complete backup of the current Archer database and configuration
- Test the upgrade in a non-production/staging environment before applying to production
- Upgrade Archer to version 6.9.3.1 or later following the official upgrade documentation
- Verify the XSS vulnerability is resolved by testing the reflected input vector
- Deploy the verified upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26947 — 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-26947 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