CVE-2017-10962
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 · uneditedREDCap before 7.5.1 has XSS via the query string.
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 confidenceREDCap versions before 7.5.1 contain a reflected Cross-Site Scripting (XSS) vulnerability where malicious script can be injected via the query string parameters. When a user clicks a crafted URL, the unsanitized input is executed in their browser, potentially allowing session hijacking or credential theft.
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<= 7.5.0CVSS 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.0/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 installationLocate the Redcap web application in your environment. This is typically installed on a web server and may be found in common web directories (for example, /var/www/html/redcap or C:\inetpub\wwwroot\redcap). Verify that the application is accessible via browser or file system.Affected if Redcap is not installed in the environment, this CVE does not apply.
-
Determine installed Redcap versionAccess the Redcap interface and navigate to the version information. This is commonly found by logging into the application and checking the 'Control Center' or by viewing the version file included in the installation directory (typically named version.txt or displayed on the login page). Alternatively, check the header/footer of any Redcap page for version text, or review installation documentation for version location.Affected if The version cannot be determined, further investigation may be needed to confirm the installation.
-
Compare version to affected rangeReview the identified version number. Affected versions are 7.5.0 and earlier. Versions 7.5.1 and later include the fix. Compare your installed version number to these boundaries.Affected if The installed version is 7.5.0 or earlier (for example, 7.5.0, 7.4.0, 7.3.0, etc.), the environment falls within the affected range for this CVE.
-
Confirm query string handlingThe vulnerability allows malicious script injection via URL query string parameters. This is a code-level flaw present in the affected versions and does not require a specific configuration setting to be enabled. No special module or feature check is needed beyond version confirmation.Affected if Version is confirmed as 7.5.0 or earlier, the vulnerability is present regardless of configuration.
If Redcap is installed and the version is 7.5.0 or earlier, the environment is affected by this reflected XSS vulnerability in query string parameters.
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 dataUpgrade REDCap to version 7.5.1 or later, which includes proper input sanitization for query string parameters. If immediate upgrading is not possible, implement web application firewall rules to filter malicious query string patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10962 — 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-2017-10962 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