CVE-2022-26949
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 SP2 P1 (6.9.2.1) contains an improper access control vulnerability on attachments. A remote authenticated malicious user could potentially exploit this vulnerability to gain access to files that should only be allowed by extra privileges.
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 confidenceRSA Archer versions 6.x through 6.9 SP2 P1 (6.9.2.1) contains an improper access control vulnerability in the attachment handling functionality. An authenticated remote user can exploit this to access files that should require elevated privileges, bypassing the intended access control restrictions on attachments.
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.2.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Determine RSA Archer installation versionLocate the RSA Archer version information through the Archer Control Panel, the About page in the Archer web interface, or by checking the installation directory for version metadata filesAffected if The installed version is 6.1.0.0 through 6.9.2.1 (any version >= 6.1.0.0 and < 6.9.2.2)
-
Verify version is within affected rangeCompare your identified version against the vulnerable range: versions 6.1.0.0 through 6.9.2.1 are affected; version 6.9.2.2 and later are patchedAffected if The version falls within >= 6.1.0.0 and < 6.9.2.2
-
Confirm attachment handling functionality is accessibleVerify that the RSA Archer web application is operational and the attachment upload/download feature is available to usersAffected if The attachment handling module is active and users can interact with file attachments in the application
You are affected if RSA Archer version 6.1.0.0 through 6.9.2.1 is installed and the attachment handling functionality is accessible to authenticated users.
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.2.2
Apply the vendor-provided security patch for CVE-2022-26949 to affected Archer installations. Restrict attachment access permissions to the minimum required until the patch is deployed.
Archer 6.9.2.2 or later
- 1. Review the Archer upgrade documentation and release notes for version 6.9.2.2 or later
- 2. Schedule a maintenance window for the upgrade process
- 3. Perform a complete backup of the Archer database and configuration files
- 4. Verify system prerequisites for the target version (6.9.2.2 or later) are met
- 5. Execute the upgrade following the official Archer upgrade procedure
- 6. After upgrade, verify that the attachment access control vulnerability is resolved
- 7. Test that normal attachment functionality works as expected
- 8. Confirm proper privilege enforcement for file access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26949 — 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-26949 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