Skip to main content
CVE-2024-51379VulnerabilityPublished Updated

CVE-2024-51379: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 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

AI-suggested

Organizations should immediately review and sanitize all user inputs in the description fields, employing strict input validation and output encoding to prevent script injection. Implement Content Security Policy (CSP) headers to restrict script execution origins. Limit admin access and monitor admin activities for suspicious behavior. Regularly update JATOS to the latest version once a patch is released. In the interim, restrict who can submit or edit study descriptions and conduct manual reviews before publishing. Employ web application firewalls (WAFs) with rules to detect and block XSS payloads targeting JATOS. Educate administrators about the risk of clicking on untrusted content within the platform.

Description

Stored Cross-Site Scripting (XSS) vulnerability discovered in JATOS v3.9.3. The vulnerability exists in the description component of the study section, where an attacker can inject JavaScript into the description field. This allows for the execution of malicious scripts when an admin views the description, potentially leading to account takeover and unauthorized actions.

References

Community reviews

Loading reviews…