CVE-2024-39125
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 · uneditedRoundup before 2.4.0 allows XSS via a SCRIPT element in an HTTP Referer header.
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 confidenceRoundup issue tracking software before version 2.4.0 contains a reflected Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected via a SCRIPT element in the HTTP Referer header. When a user visits a crafted link, the Referer header value is rendered without proper sanitization, allowing script execution in the victim's browser.
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< 2.4.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 Roundup Tracker versionCheck your installed Roundup version using the package manager, source code version file, or the application's admin interface version displayAffected if the installed version is before 2.4.0
-
Confirm Roundup web interface is activeVerify that the Roundup web interface is accessible and running, as this XSS targets users visiting crafted links through the browserAffected if the web interface is exposed and accessible to users
-
Verify Referer header handlingCheck if inbound HTTP requests preserve and reflect the Referer header in any web responses. This can be tested by sending a request with a malicious Referer header and observing if it is reflected unsanitized in the responseAffected if the application reflects the Referer header value in its response without sanitization
You are affected if your Roundup Tracker installation is version 2.4.0 or earlier and the web interface is accessible to users who could click crafted links.
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 · scoped2.4.0
Upgrade Roundup to version 2.4.0 or later, which contains the fix for this XSS vulnerability. If immediate upgrading is not possible, implement input validation on the Referer header before rendering.
2.4.0
- Verify current Roundup version by checking the installed version or the admin interface
- Create a complete backup of the Roundup database and configuration files
- Stop the Roundup web service before performing the upgrade
- Upgrade Roundup to version 2.4.0 or later using the standard upgrade method for your installation (e.g., package manager, pip, or source installation)
- Verify the upgrade was successful by checking the new version number
- Restart the Roundup web service
- Test that the application functions normally after the upgrade
- Validate that the XSS vulnerability is fixed by confirming the Referer header is properly sanitized (the fixed version should escape or filter script elements in the Referer header)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39125 — 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-39125 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