DrupalCMS
CVE-2016-7571
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 · uneditedCross-site scripting (XSS) vulnerability in Drupal 8.x before 8.1.10 allows remote attackers to inject arbitrary web script or HTML via vectors involving an HTTP exception.
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 confidenceCross-site scripting (XSS) vulnerability in Drupal 8.x before 8.1.10 allows remote attackers to inject arbitrary web script or HTML via HTTP exception vectors. The vulnerability exists in how Drupal handles HTTP exceptions, potentially allowing malicious script execution when exceptions are rendered.
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
DrupalCMS
= 8.0.0= 8.0.1= 8.0.2= 8.0.3= 8.0.4= 8.0.5= 8.0.6= 8.1.0= 8.1.1= 8.1.2= 8.1.3= 8.1.4CVSS 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.
-
Determine installed Drupal core versionCheck the VERSION constant in Drupal's core/lib/Drupal.php file, or look at the CHANGELOG.txt file in the Drupal root directory, or run: composer show drupal/core 2>/dev/null | grep versionAffected if The installed version is 8.0.0 through 8.1.4 inclusive
-
Confirm HTTP exception handling is in useThis vulnerability affects default HTTP exception handling in Drupal 8 - no specific configuration needs to be checked as the flaw exists in core exception renderingAffected if Any HTTP error response (404, 403, etc.) can trigger the vulnerable code path in affected versions
-
Verify exception subscriber configurationInspect the core/modules/system/src/EventSubscriber/ExceptionJsonRenderer.php or similar exception subscriber classes for how they handle and serialize HTTP exceptionsAffected if The site uses Drupal's default exception handling without custom sanitization overrides
A Drupal 8 installation is affected if it runs any version from 8.0.0 through 8.1.4, as the XSS vulnerability exists in the core HTTP exception rendering code of those versions.
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 Drupal 8.x to version 8.1.10 or later to patch the XSS vulnerability in HTTP exception handling. If immediate patching is not possible, review and sanitize custom exception handlers.
Fix this in Drupal
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7571 — 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-2016-7571 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