CVE-2025-23111: Vanderbilt REDCap · XSS or 'Cross-site Scripting'
Affects Vanderbilt REDCapSource CVE Database V5
Not known to be exploited · CVSS 4.7 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jan 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubping-oui-no/REDCappkg:github/ping-oui-no/REDCapOther threats | Affected
| Fixed in– |
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-2025-23111, organizations should implement the following specific measures: 1) Immediately review and sanitize all user-supplied input fields, especially the Survey field names, using strict whitelist-based input validation and proper HTML entity encoding to prevent injection of malicious HTML or scripts. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and limit redirection capabilities. 3) Educate survey recipients and users about the risk of clicking unexpected or suspicious links within surveys, emphasizing verification of URLs before interaction. 4) Monitor survey content for anomalous or suspicious field names that could indicate attempted exploitation. 5) If possible, temporarily disable or restrict the ability to create or modify survey field names until a vendor patch is available. 6) Coordinate with Vanderbilt for timely updates and patches, and plan for rapid deployment once available. 7) Implement web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the Survey field name parameter. 8) Conduct regular security assessments and penetration testing focused on input validation and XSS vulnerabilities in REDCap deployments. These targeted actions go beyond generic advice by focusing on the specific injection vector and user interaction pattern of this vulnerability.
Description
An issue was discovered in REDCap 14.9.6. It allows HTML Injection via the Survey field name, exposing users to a redirection to a phishing website. An attacker can exploit this to trick the user that receives the survey into clicking on the field name, which redirects them to a phishing website. Thus, this allows malicious actions to be executed without user consent.