CVE-2024-37396VulnerabilityPublished 10 Jun 2025

CVE-2024-37396: n/a

Source CVE Database V5

Not known to be exploited : upgrade to 14.2.1 soon.

Data as of 26 Oct 2026, 07:57 UTC

Severity

High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 14.2.1

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redcap/redcap to 14.2.1.

Affected software

Product	Affected	Fixed in
GitHubredcap/redcap`pkg:github/redcap/redcap`Other threats	Affected <14.2.1	Fixed in 14.2.1

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

AI-suggested

European organizations using REDCap should prioritize upgrading to version 14.2.1 or later immediately to remediate this vulnerability. If you cannot patch yet, implement strict access controls to limit authenticated user permissions, especially restricting calendar event creation and editing to trusted personnel only. Conduct thorough input validation and sanitization on the 'Notes' field at the application level if possible, to detect and block malicious payloads. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing REDCap. Regularly audit calendar events for suspicious or unexpected content. Enhance monitoring and logging to detect anomalous user behavior that could indicate exploitation attempts. Educate users about the risks of XSS and encourage vigilance when interacting with calendar events. Finally, ensure that incident response plans include scenarios involving web application XSS attacks to enable rapid containment and remediation.

Description

A stored cross-site scripting (XSS) vulnerability in the Calendar function of REDCap 13.1.9 allows authenticated users to execute arbitrary web script or HTML by injecting a crafted payload into the 'Notes' field of a calendar event. This could lead to the execution of malicious scripts when the event is viewed. Updating to version 14.2.1 or later is recommended to remediate this vulnerability.

Impact

For European organizations, particularly those in healthcare, academic research, and clinical trial sectors where REDCap is commonly deployed, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to sensitive personal health information (PHI) and research data, violating GDPR and other data protection regulations. The ability to execute arbitrary scripts could also facilitate lateral movement within the network, privilege escalation, or the deployment of ransomware or other malware. The stored nature of the XSS means multiple users could be affected once the malicious payload is injected, amplifying the potential damage. Additionally, reputational harm and regulatory penalties could result from data breaches stemming from this vulnerability. Given the criticality of data handled by REDCap, the impact on confidentiality and integrity is particularly concerning, while availability may also be indirectly affected if systems are compromised or taken offline for remediation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 20:02 UTC

Technical details

References

Community reviews

Related threats