CVE-2022-26950
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 P2 (6.9.0.2) is affected by an open redirect vulnerability. A remote unprivileged attacker may potentially redirect legitimate users to arbitrary web sites and conduct phishing attacks. The attacker could then steal the victims' credentials and silently authenticate them to the Archer application without the victims realizing an attack occurred.
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 confidenceArcher 6.x through 6.9 P2 (6.9.0.2) contains an open redirect vulnerability allowing unprivileged remote attackers to redirect authenticated users to arbitrary external websites. This enables phishing attacks where credentials can be stolen and users silently re-authenticated to the Archer application without detecting the compromise.
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.0.3CVSS 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 installed Archer versionLog into the Archer web application as an administrator and navigate to About page (typically /Archer/home/about.aspx) or check the installation directory for version.txt or similar version fileAffected if Version displayed is 6.1.0.0 through 6.9.0.2 (inclusive)
-
Compare version against CVE rangeVerify the exact version number from step 1 against the affected range: versions >= 6.1.0.0 and < 6.9.0.3Affected if Installed version is 6.1.0.0, 6.2.x, 6.3.x, 6.4.x, 6.5.x, 6.6.x, 6.7.x, 6.8.x, or any 6.9.0.x version up to and including 6.9.0.2
-
Confirm Archer web component is accessibleAttempt to access the Archer login page via browser to confirm the web application is running and exposedAffected if Web interface is reachable and version is within the affected range listed in step 2
Your environment is affected if the installed RSA Archer version falls between 6.1.0.0 and 6.9.0.2 inclusive.
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.0.3
Apply the vendor patch or upgrade to a version beyond 6.9 P2 (6.9.0.2) as specified in the official Archer security advisory.
Archer 6.9.0.3 or later
- 1. Review the Archer upgrade documentation for your current version
- 2. Ensure you have a complete backup of the Archer database and application files
- 3. Schedule a maintenance window for the upgrade
- 4. Download the Archer 6.9.0.3 (or later) installation package from the RSA Archer community portal
- 5. Follow the standard Archer upgrade procedure: stop Archer services, run the installer, verify database upgrades, restart services
- 6. After upgrade, verify the open redirect vulnerability is resolved by testing the affected URL parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26950 — 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-26950 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