CVE-2023-32761
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 · uneditedCross Site Request Forgery (CSRF) vulnerability in Archer Platform before v.6.13 and fixed in v.6.12.0.6 and v.6.13.0 allows an authenticated attacker to execute arbitrary code via a crafted request.
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 confidenceCross Site Request Forgery (CSRF) vulnerability in RSA Archer Platform allows an authenticated attacker to execute arbitrary code by tricking a user's authenticated browser into sending a crafted request to the platform. The vulnerability exists in versions before v6.13 (fixed in v6.12.0.6 and v6.13.0).
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.12.0.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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 RSA Archer Platform versionLog into the Archer administration console or check the software inventory/system information page for the current platform version numberAffected if The displayed version is lower than 6.12.0.6 (or between 6.12.0.0 and 6.12.0.5) or shows a version prior to 6.13.0
-
Verify the exact version stringConfirm the full version number including patch level (for example, 6.11.0.0, 6.12.0.0, 6.12.0.5) from the About or System Information section of the Archer UIAffected if The version starts with 6.12.0.0 through 6.12.0.5, or is any version below 6.12.0.6 that is not 6.13.0 or higher
-
Check for available version documentationReview any internal change logs, release notes, or system documentation that references the currently deployed Archer versionAffected if Documentation shows the installed version is any release prior to the v6.12.0.6 or v6.13.0 patch releases
You are affected if your deployed RSA Archer Platform version is any release below 6.12.0.6 or below 6.13.0, as these are the versions that contain the CSRF vulnerability fix.
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.12.0.6
Upgrade to Archer Platform v6.12.0.6 or v6.13.0 or later. Implement anti-CSRF tokens and validate Origin/Referer headers on sensitive endpoints as additional defense-in-depth measures.
6.12.0.6 or 6.13.0
- Identify the current Archer Platform version by accessing the system or administration console
- Plan and schedule an upgrade to version 6.12.0.6 or 6.13.0 (either version contains the security fix)
- Create a full backup of the Archer system including database and configuration files
- Follow the official Archer Platform upgrade documentation to apply the update
- After upgrade, verify the system is running version 6.12.0.6 or higher and confirm all services are operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32761 — 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-2023-32761 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