CVE-2024-41705
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 · uneditedA stored XSS issue was discovered in Archer Platform 6.8 before 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) and 6.13 P4 (6.13.0.4) are also fixed releases. This vulnerability is similar to, but not identical to, CVE-2023-30639.
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 confidenceA stored XSS vulnerability in RSA Archer Platform versions 6.8 before 2024.06 allows authenticated users to inject malicious HTML/JavaScript into application data stores. When victim users access the compromised data through their browsers, the payload executes in the application's security context, potentially enabling session hijacking, credential theft, or unauthorized actions.
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.0.4>= 6.14.0, < 6.14.0.4>= 2024.03, < 2024.06CVSS 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 RSA Archer Platform versionAccess the Archer Platform Administration menu or check the About page to view the exact version number. This is typically found under Help > About or in the system information section of the administrative console.Affected if The installed version falls within these ranges: < 6.13.0.4; >= 6.14.0 and < 6.14.0.4; >= 2024.03 and < 2024.06
-
Confirm authentication is enabledVerify that user authentication is active in the Archer Platform. This vulnerability requires an authenticated user to inject the malicious payload, so confirm whether local or federated user logins are permitted.Affected if Authentication is enabled and users can log in to the platform (the attack vector requires authenticated access)
-
Inspect stored data fields for suspicious script contentReview application data records, particularly fields that accept free-form text input (such as description fields, comment fields, or custom questionnaire answers). Look for HTML script tags, JavaScript event handlers, or encoded script payloads.Affected if Any stored records contain unsanitized HTML/JavaScript content that could execute in a user's browser
-
Test data rendering in browserLog in as a standard user (different from the account that might have injected content) and view records containing free-form text fields. Open browser developer tools and check the Console for JavaScript errors or examine the DOM to see if raw script tags or event handlers are present in the rendered HTML.Affected if Rendered HTML contains unencoded script tags or JavaScript event handlers that could execute
-
Review application audit logsAccess the Archer Platform audit logs or security event logs. Search for entries indicating cross-site scripting attempts, unusual HTML characters in data fields, or security filter triggers.Affected if Logs show evidence of XSS payloads being stored or attempted injection patterns
A user is affected if they are running any RSA Archer Platform version below 6.13.0.4, between 6.14.0 and 6.14.0.4, or between 2024.03 and 2024.06, and if the application contains stored data with unsanitized script content that renders in users' browsers.
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.46.14.0.42024.06
Upgrade to Archer Platform 6.8 2024.06 or later, or apply patched releases 6.14.P4/6.13 P4. Implement output encoding and input validation as defense-in-depth measures.
Upgrade to 6.13.0.4 (6.13 P4), 6.14.0.4 (6.14 P4), or 2024.06 depending on your current branch
- 1. Identify the current Archer Platform version by navigating to Setup > System Settings > About in the Archer web interface
- 2. If running a version < 6.13.0.4, upgrade directly to version 6.13.0.4 (6.13 P4) or later
- 3. If running version 6.14.0.x where x < 4, upgrade to version 6.14.0.4 (6.14 P4) or later
- 4. If running version 2024.03 through 2024.05.x, upgrade to version 2024.06 or later
- 5. After upgrade, verify the new version is correctly installed by checking Setup > System Settings > About
- 6. Test that the application functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41705 — 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-2024-41705 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