dbcve.org
DrupalCMS

CVE-2017-6929

MEDIUM · 6.1 CVSS v3.0 Published 2018-03-01
Fix available
A fix is available. Upgrade to 7.57 / 8.4.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A jQuery cross site scripting vulnerability is present when making Ajax requests to untrusted domains. This vulnerability is mitigated by the fact that it requires contributed or custom modules in order to exploit. For Drupal 8, this vulnerability was already fixed in Drupal 8.4.0 in the Drupal core upgrade to jQuery 3. For Drupal 7, it is fixed in the current release (Drupal 7.57) for jQuery 1.4.4 (the version that ships with Drupal 7 core) as well as for other newer versions of jQuery that might be used on the site, for example using the jQuery Update module.

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 confidence

This is a jQuery cross-site scripting (XSS) vulnerability in Drupal that allows malicious code execution when making Ajax requests to untrusted domains. The vulnerability requires contributed or custom modules to be exploitable. It was patched in Drupal 8.4.0 (by upgrading to jQuery 3) and Drupal 7.57 (which includes the fix for jQuery 1.4.4 and supports newer jQuery versions via the jQuery Update module).

MitigationUpdate to Drupal 7.57 or Drupal 8.4.0 or later, and ensure jQuery is updated to a patched version (jQuery 3 for Drupal 8, or any patched version via jQuery Update module for Drupal 7).

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
Affected:>= 7.0, < 7.57>= 8.0.0, < 8.4.0
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Drupal core version
    Run `drush status` or check the VERSION file in the Drupal root directory (usually at /var/www/html/core/lib/Drupal.php or look for CHANGELOG.txt with version info). Alternatively, access admin/reports/status and look for the Drupal core version.
    Affected if The installed version is between 7.0 and 7.56, or between 8.0.0 and 8.3.x (any version before 7.57 or 8.4.0).
  2. Determine jQuery version in use
    For Drupal 7: Check if the jQuery Update module is installed at admin/modules and its version. Then inspect the actual jQuery file loaded in the browser by opening developer tools (F12), going to the Console, and typing `$.fn.jquery` or checking the source of jquery.js or jquery.min.js in the page source. For Drupal 8: Check the libraries directory (core/assets/vendor/jquery).
    Affected if jQuery version is 1.x (particularly 1.4.4 or earlier without patches) in Drupal 7, or jQuery 2.x in Drupal 8 versions before 8.4.0.
  3. Audit modules making Ajax requests
    Review contributed and custom modules for JavaScript code that makes Ajax requests using jQuery $.ajax(), $.get(), or $.post() to external (untrusted) domains. Search codebases for '$.ajax', '$.get', '$.post', and 'url:' patterns pointing to non-internal domains. Check module README files or API documentation.
    Affected if Modules exist that perform Ajax requests to untrusted or external domains using jQuery, and these modules are enabled.
  4. Verify jQuery Update module configuration (Drupal 7)
    Navigate to admin/config/system/jquery_update (if the jQuery Update module is installed) and check the jQuery version configured for each page region. Also verify the module version at admin/modules or in the jQuery Update module's .info file.
    Affected if jQuery Update module is absent, disabled, or configured with an unpatched jQuery version (older than any patched version available via the module).

A system is affected if it runs Drupal 7.x below 7.57 or Drupal 8.x below 8.4.0, uses an unpatched jQuery version, and has enabled modules that make Ajax requests to untrusted external domains.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 7.57 / 8.4.0 or later
Fixed in 7.578.4.0
Interim mitigation

Update to Drupal 7.57 or Drupal 8.4.0 or later, and ensure jQuery is updated to a patched version (jQuery 3 for Drupal 8, or any patched version via jQuery Update module for Drupal 7).

Fix this in Drupal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6929 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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