# CVE-2017-6929: Drupal cross site scripting vulnerability

> Cross-site scripting in jQuery allows attackers to execute scripts when making Ajax requests to untrusted domains, requiring custom modules for exploitation.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5vpr-v24w-mmjj, UBUNTU-CVE-2017-6929

## What is CVE-2017-6929?

CVE-2017-6929 is a medium-severity cross-site scripting vulnerability in Debian Debian Linux, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2017-6929?

8 open source packages ship an affected version, including drupal/core and drupal/drupal. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 7.0 | 7.57 |
| `drupal/core` | Packagist | From 7.0 | 7.57 |
| `drupal/core` | Packagist | From 8.0 | 8.4.0 |
| `drupal/core` | Packagist | From 8.0 | 8.4.0 |
| `drupal/drupal` | Packagist | From 7.0 | 7.57 |
| `drupal/drupal` | Packagist | From 7.0 | 7.57 |
| `drupal/drupal` | Packagist | From 8.0 | 8.4.0 |
| `drupal/drupal` | Packagist | From 8.0 | 8.4.0 |

Products: Debian Debian Linux, Drupal Drupal.

## How do I fix CVE-2017-6929?

Upgrade drupal/core to a fixed version for your release line: 7.57 or 8.4.0.

## Is CVE-2017-6929 being exploited?

There is no known exploitation of CVE-2017-6929 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6929 and fix it if it is affected.

What it is: CVE-2017-6929 is a medium-severity cross-site scripting vulnerability in Debian Debian Linux, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6929 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 7.0; fixed in 7.57
- drupal/core (Packagist): affected from 7.0; fixed in 7.57
- drupal/core (Packagist): affected from 8.0; fixed in 8.4.0
- drupal/core (Packagist): affected from 8.0; fixed in 8.4.0
- drupal/drupal (Packagist): affected from 7.0; fixed in 7.57
- drupal/drupal (Packagist): affected from 7.0; fixed in 7.57
- drupal/drupal (Packagist): affected from 8.0; fixed in 8.4.0
- drupal/drupal (Packagist): affected from 8.0; fixed in 8.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6929/ (Markdown: https://insights.sbomify.com/CVE-2017-6929/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6929
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6929
- OSV: https://osv.dev/vulnerability/CVE-2017-6929

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6929/
Summaries are generated and may contain mistakes; the official description above is the record.