CVE-2024-26313
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 · uneditedArcher Platform 6.x before 6.14 P2 HF2 (6.14.0.2.2) contains a stored cross-site scripting (XSS) vulnerability. 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.13.P3 HF1 (6.13.0.3.1) 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 confidenceArcher Platform versions before 6.14 P2 HF2 (6.14.0.2.2) and 6.13.P3 HF1 (6.13.0.3.1) contain a stored cross-site scripting vulnerability. An authenticated remote attacker can inject malicious HTML or JavaScript code into application data stores. When other users access this data through their browsers, the malicious code executes in the context of the vulnerable application, potentially allowing session hijacking or credential theft.
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.3.1>= 6.14.0, < 6.14.0.2.2CVSS 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 versionLocate the version information in the Archer application UI (typically under Help > About) or check installation documentation and system files for the installed version numberAffected if The displayed version number is less than 6.13.0.3.1, or is 6.14.0.0.0 through 6.14.0.2.1 inclusive
-
Confirm the major version branchDetermine whether the installation is on the 6.13.x branch or the 6.14.x branch based on the version identified in the previous stepAffected if The version falls into either the 6.13.x series before 6.13.0.3.1, or the 6.14.x series before 6.14.0.2.2
-
Verify vulnerability context is applicableConfirm that the Archer instance allows authenticated users to create or modify data records, as this stored XSS requires an authenticated attacker to inject malicious code into application data fieldsAffected if The instance has active user accounts with permissions to input or modify application data, and those data fields are rendered in user browsers
If the installed version is 6.13.x before 6.13.0.3.1, or 6.14.x before 6.14.0.2.2, the environment is affected by this stored XSS vulnerability.
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.3.16.14.0.2.2
Upgrade Archer Platform to version 6.14 P2 HF2 (6.14.0.2.2) or 6.13.P3 HF1 (6.13.0.3.1). Additionally, implement input validation and output encoding for all user-supplied data stored in the application, and consider implementing Content Security Policy headers.
6.14 P2 HF2 (6.14.0.2.2) or 6.13.P3 HF1 (6.13.0.3.1)
- 1. Identify the current version of Archer Platform installed in your environment
- 2. If running a version < 6.13.0.3.1, upgrade to 6.13.P3 HF1 (6.13.0.3.1) or later
- 3. If running a version >= 6.14.0 but < 6.14.0.2.2, upgrade to 6.14 P2 HF2 (6.14.0.2.2) or later
- 4. After upgrade, verify the XSS vulnerability is remediated by testing that user-supplied data in application data stores is properly sanitized
- 5. Conduct standard post-upgrade validation to ensure all Archer functionalities operate correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26313 — 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-26313 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