dbcve.org
RoundupApplication · Roundup Tracker

CVE-2024-39124

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-17
Fix available
A fix is available. Upgrade to 2.4.0 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
In Roundup before 2.4.0, classhelpers (_generic.help.html) allow XSS.

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

Roundup bug tracker before version 2.4.0 contains a cross-site scripting (XSS) vulnerability in the classhelpers module, specifically in the _generic.help.html template. The vulnerability allows attackers to inject malicious scripts through user-controlled input that is not properly sanitized or encoded when rendered in the help pages.

MitigationUpgrade to Roundup version 2.4.0 or later, which contains the fix for this XSS vulnerability. If upgrading is not immediately possible, implement output encoding/sanitization on all user-supplied data before rendering in the _generic.help.html template.

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
RoundupApplication
Affected:< 2.4.0

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. Determine installed Roundup version
    Locate the Roundup installation and check its version number (typically in a version file, setup.py, or release notes). Compare this version to the affected range: versions before 2.4.0 are vulnerable.
    Affected if The installed version is less than 2.4.0 (e.g., 2.3.0, 2.2.x, etc.)
  2. Locate the classhelpers module
    Find the classhelpers module directory within the Roundup installation. This module contains the vulnerable _generic.help.html template.
    Affected if The classhelpers module exists and contains a _generic.help.html file
  3. Inspect the _generic.help.html template
    Open the _generic.help.html template file in the classhelpers module and examine how user-supplied data is rendered. Look for template variables that output user input without proper HTML encoding (e.g., missing |html filter or equivalent escaping in the templating system).
    Affected if The template contains unsanitized user input that renders directly into HTML without encoding
  4. Verify help pages are accessible
    Confirm that the help functionality utilizing _generic.help.html is enabled and accessible in the deployed Roundup instance. Check if users can view help pages.
    Affected if Help pages are accessible to users who could inject malicious scripts through user-controlled fields

A user is affected if running a Roundup version earlier than 2.4.0 AND the help template contains unsanitized user input rendering in HTML output.

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 2.4.0 or later
Fixed in 2.4.0
Interim mitigation

Upgrade to Roundup version 2.4.0 or later, which contains the fix for this XSS vulnerability. If upgrading is not immediately possible, implement output encoding/sanitization on all user-supplied data before rendering in the _generic.help.html template.

Recommended fix Moderate confidence

2.4.0

  1. 1. Identify the current version of Roundup installation by checking the version file or running the version command
  2. 2. Create a complete backup of the current Roundup installation including database and configuration files
  3. 3. Upgrade Roundup to version 2.4.0 or later by following the project's standard upgrade procedure
  4. 4. After upgrade, verify that _generic.help.html no longer contains the vulnerable classhelpers that allowed XSS
  5. 5. Test that the application functions correctly after the upgrade

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

Fix this in Roundup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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