dbcve.org
ArcherApplication · Archerirm

CVE-2024-41706

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-25
Fix available
A fix is available. Upgrade to 6.14.0.4 / 2024.06 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
A stored XSS issue was discovered in Archer Platform 6 before version 2024.06. A remote authenticated malicious Archer user could potentially exploit this 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 P4 (6.14.0.4) 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

A stored cross-site scripting (XSS) vulnerability in RSA Archer Platform versions prior to 2024.06 allows authenticated users to inject malicious HTML or JavaScript code into the application's trusted data store. When other users access the compromised data through their browsers, the injected script executes in the context of the vulnerable application.

MitigationUpgrade Archer Platform to version 2024.06 or 6.14.0.4 (6.14 P4) which contain the security fix for this stored XSS 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.14.0.4>= 2024.03, < 2024.06

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. Check RSA Archer Platform version in admin interface
    Log into the Archer Platform as an administrator and navigate to the About or System Information page, typically found under Administration > System > About. Record the exact version number displayed.
    Affected if The version shown is less than 6.14.0.4 OR is 2024.03.x through 2024.05.x (any version from 2024.03 up to but not including 2024.06)
  2. Check version via Archer Control Panel
    Open the RSA Archer Control Panel on the server and look at the Build Number displayed in the main window. This shows the exact version and build information.
    Affected if The Build Number is below 6.14.0.4 or falls within the 2024.03 through 2024.05 release range
  3. Check installation directory for version file
    On the Archer application server, navigate to the installation directory (commonly in C:\Program Files\RSA Archer\ or similar) and look for a version.txt, about.xml, or similar file that contains build information.
    Affected if The version file shows a build number prior to 6.14.0.4 or within the 2024.03-2024.05 range

You are affected if your installed RSA Archer Platform version is any release prior to 6.14.0.4, or any release from the 2024.03, 2024.04, or 2024.05 release trains.

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.14.0.4 / 2024.06 or later
Fixed in 6.14.0.42024.06
Interim mitigation

Upgrade Archer Platform to version 2024.06 or 6.14.0.4 (6.14 P4) which contain the security fix for this stored XSS vulnerability.

Recommended fix High confidence

2024.06 or later (or 6.14.0.4/6.14 P4 for 6.14.x track)

  1. 1. Identify the current installed version of Archer Platform by checking the About or System Information section in the Archer administration console.
  2. 2. Determine which upgrade path applies: if running version 2024.03, 2024.04, or 2024.05, upgrade to version 2024.06 or later; if running version 6.14.x before 6.14.0.4, upgrade to version 6.14.0.4 (6.14 P4) or later.
  3. 3. Download the appropriate fixed release from the RSA Archer customer portal or official distribution channels.
  4. 4. Review the Archer Platform upgrade guide and release notes for pre-upgrade requirements including backup procedures, system prerequisites, and any prerequisite patches.
  5. 5. Execute the upgrade following the documented upgrade procedure, ensuring proper system backup before proceeding.
  6. 6. After upgrade completion, verify the fix by logging in as an authenticated user and confirming the XSS vulnerability is no longer exploitable in the application data store functionality.

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

Fix this in Archer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41706 — 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-2024-41706 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