Skip to main content
CVE-2024-39124VulnerabilityPublished Updated

CVE-2024-39124: roundup · n/a

Affects roundupSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium : upgrade to 2.4.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade roundup to 2.4.0.

Affected software

ProductAffectedFixed in
PyPIrounduppkg:pypi/roundupOther threatsAffected
  • <2.4.0
Fixed in
  • 2.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-39124, organizations should upgrade Roundup to version 2.4.0 or later once the patch is officially released, as this will include proper input sanitization fixes. Until then, administrators can implement strict input validation and output encoding on any user-supplied data rendered in help pages or related components. Employing Content Security Policy (CSP) headers can reduce the impact of injected scripts by restricting script execution sources. Additionally, educating users to avoid clicking suspicious links or interacting with untrusted content within the Roundup interface can reduce exploitation likelihood. Regularly monitoring logs for unusual activity and applying web application firewalls (WAFs) with rules targeting XSS patterns may provide temporary protection. Finally, reviewing and limiting user permissions within Roundup can minimize potential damage if an account is compromised.

Description

In Roundup before 2.4.0, classhelpers (_generic.help.html) allow XSS.

References

Community reviews

Loading reviews…