dbcve.org
ArcherApplication · Archerirm

CVE-2023-45358

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 6.13.0.2.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Archer Platform 6.x before 6.13 P2 HF2 (6.13.0.2.2) contains a stored cross-site scripting (XSS) vulnerability. A remote authenticated malicious Archer user could potentially exploit this vulnerability to store malicious HTML or JavaScript code in a trusted application data store. When victim users access the data store through their browsers, the malicious code gets executed by the web browser in the context of the vulnerable application. 6.14 (6.14.0) is also a fixed release.

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 confidence

This is a stored cross-site scripting (XSS) vulnerability in RSA Archer Platform versions prior to 6.13 P2 HF2 (6.13.0.2.2). An authenticated malicious user can inject malicious HTML or JavaScript code into the application's data store. When other users view this data through their browsers, the injected code executes in the context of the vulnerable application, potentially leading to session hijacking, credential theft, or other client-side attacks.

MitigationUpgrade to Archer Platform version 6.13 P2 HF2 (6.13.0.2.2), version 6.14 (6.14.0), or later to remediate this vulnerability.

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
ArcherApplication
Affected:>= 6.0, < 6.13.0.2.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RSA Archer Platform version
    Access the Archer Platform administrative interface or check the installation documentation. Navigate to the About or System Information section in the Archer UI, or query the system configuration file or database that stores the application version.
    Affected if The installed version is 6.0 or higher but lower than 6.13.0.2.2
  2. Confirm the application is running and accessible
    Verify that the Archer Platform web interface is currently accessible by attempting to load the login page or an authenticated page in a browser.
    Affected if The application is accessible and accepts user authentication, which is required for the stored XSS to be exploitable
  3. Determine if user input forms are exposed
    Log into the Archer Platform and navigate to common data entry areas such as questionnaire responses, custom record fields, or data feed inputs where users can submit content that gets stored in the application.
    Affected if User-submitted content can be stored and later displayed to other users, creating the conditions for stored XSS

A user is affected if their installed Archer Platform version falls within the range of 6.0 to 6.13.0.2.1 (inclusive), since versions below 6.13.0.2.2 contain the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.13.0.2.2 or later
Fixed in 6.13.0.2.2
Interim mitigation

Upgrade to Archer Platform version 6.13 P2 HF2 (6.13.0.2.2), version 6.14 (6.14.0), or later to remediate this vulnerability.

Recommended fix High confidence

6.13.0.2.2 (6.13 P2 HF2) or 6.14.0

  1. 1. Review the Archer Platform upgrade documentation and release notes for version 6.13.0.2.2 or 6.14.0 to understand prerequisites and compatibility requirements.
  2. 2. Perform a full backup of the Archer database and configuration files before initiating the upgrade.
  3. 3. Schedule a maintenance window as upgrades typically require downtime.
  4. 4. Download the appropriate upgrade package (6.13 P2 HF2 or 6.14.0) from the RSA Archer customer portal or official distribution channel.
  5. 5. Follow the standard Archer Platform upgrade procedure: stop Archer services, run the upgrade installer, validate the installation, and restart services.
  6. 6. Verify the upgrade was successful by logging into the Archer interface and checking the version number.
  7. 7. Test critical workflows and custom calculations to ensure functionality is intact after the upgrade.
Caveat Standard upgrade risks apply - review release notes for any configuration changes or deprecated features before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45358 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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