Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-6929

A jQuery cross site scripting vulnerability is present when making Aja ...

Overview

Published
1 Mar 2018
Modified
17 Jun 2026
Medium CVE
2 Registry packages
1 OS packages
1 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

6.1 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
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

Weakness: CWE-79

Affected packages · 2

Packages affected by CVE-2017-6929
EcosystemPackageVulnerableFixed in
Composer (PHP) drupal/core >=7.0, <7.57>=8.0, <8.4.0>=8.2.0, <8.3.0>=8.3.0, <8.4.0>=8.4.0, <8.4.5+2 more 7.578.4.0
Composer (PHP) drupal/drupal >=8.0, <8.4.0>=7.0, <7.57>=8.0, <8.1.0>=8.1.0, <8.2.0>=8.2.0, <8.3.0+2 more 8.4.07.57

Open a package to see all its vulnerabilities.

Operating systems · 1 fix

debian 1 release · 1 package

fixed 1
drupal7
debian fixes for CVE-2017-6929
ReleasePackageFixed in
9 drupal7 7.52-2+deb9u2

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.