CVE-2025-23112
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 · uneditedAn issue was discovered in REDCap 14.9.6. A stored cross-site scripting (XSS) vulnerability allows authenticated users to inject malicious scripts into the Survey field name of Survey. When a user receive the survey, if he clicks on the field name, it triggers the XSS payload.
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 confidenceA stored cross-site scripting (XSS) vulnerability in REDCap 14.9.6 allows authenticated users to inject malicious JavaScript into Survey field names. When survey recipients click on the affected field name, the stored XSS payload executes in their browser session.
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= 14.9.6CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Redcap installation versionCheck the Redcap installation by viewing the version number typically displayed in the Redcap admin panel, or check the version file in the Redcap installation directory if accessible.Affected if The installed version is exactly 14.9.6 (the only affected version listed)
-
Verify survey functionality is enabledCheck if surveys are enabled in the Redcap project configuration. Navigate to the project and look for survey settings or the survey queue.Affected if Surveys are enabled and the project contains active surveys with editable field names
-
Inspect survey field names in the projectOpen the data dictionary or instrument designer in Redcap and examine all field names used in surveys. Look for any field names containing HTML tags, script tags, or JavaScript event handlers.Affected if Any survey field name contains script tags, event handlers like onload/onclick, or other potentially malicious JavaScript content
-
Check database for suspicious field namesIf database access is available, query the redcap_metadata or similar table to inspect field_names for survey instruments. Look for encoded or raw script tags in field_name columns.Affected if The field_name values in the metadata table contain XSS payloads such as <script> tags or event handler attributes
-
Review survey page renderingAccess a live survey as a respondent and inspect the page source. Examine how field labels/names are rendered in the HTML.Affected if Field names are rendered without proper encoding, allowing injected JavaScript to execute when the field is clicked
A user is affected if they are running Redcap version 14.9.6 and have surveys with field names containing injected malicious script content that executes when viewed by survey respondents.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement proper output encoding/sanitization for Survey field names before rendering, and validate input on submission to prevent injection of script tags or event handlers.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23112 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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