CVE-2023-37223
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 Scripting (XSS) vulnerability in Archer Platform before v.6.13 and fixed in v.6.12.0.6 and v.6.13.0 allows a remote authenticated attacker to execute arbitrary code via a crafted malicious script.
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 confidenceCross-Site Scripting (XSS) vulnerability in RSA Archer Platform allows authenticated remote attackers to execute arbitrary JavaScript code via crafted malicious scripts injected into the platform. The vulnerability stems from insufficient input sanitization within the web interface, enabling script injection through malicious payloads that execute in users' browser contexts.
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.13.0CVSS 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 installed Archer Platform versionAccess the Archer Platform administrative interface or system configuration to locate the installed version numberAffected if The installed version is below 6.13.0 (versions prior to 6.13.0 are affected)
-
Confirm user authentication is enabledVerify that the Archer Platform web interface is configured to allow user loginsAffected if Authenticated users can access the web interface, which is required for the XSS attack to execute
-
Check for vendor patchesReview the system for any applied patches or refer to vendor release notes to confirm whether CVE-2023-37223 fixes have been implementedAffected if Patches for this vulnerability have not been applied to your environment
Your environment is affected if the installed Archer Platform version is below 6.13.0 and authenticated users can access the web interface where malicious script injection can occur.
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.13.0
Apply the vendor-supplied patches by upgrading to Archer Platform version 6.12.0.6 or 6.13.0 or later. Additionally, implement output encoding and input validation as defense-in-depth measures.
v6.12.0.6 or v6.13.0
- Identify the current version of Archer Platform running in your environment
- Review Archer Platform upgrade documentation for your current version to plan the upgrade path
- Schedule a maintenance window following your organization's change management procedures
- Perform a complete backup of the Archer database and all configuration files before proceeding
- Upgrade Archer Platform to version 6.12.0.6 OR version 6.13.0 (both contain the fix)
- After completing the upgrade, verify all services start successfully
- Confirm the system is functioning normally and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37223 — 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-37223 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