# Drupal Cross-Site Request Forgery (CSRF)

Advisory record · `GHSA-gxxq-fhc7-3jv9`

- **Identifiers:** `GHSA-gxxq-fhc7-3jv9` · `CVE-2017-6379` · `PKSA-kq9s-pmck-3hhz` · `PKSA-m9vt-xddw-ftmz`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 17 May 2022
- **Updated:** 23 Apr 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 02:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `drupal/core` (Packagist): affected `>=8.2.0, <8.2.7`; fixed in `8.2.7`
- `drupal/drupal` (Packagist): affected `>=8.2.0, <8.2.7`; fixed in `8.2.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Drupal core (drupal/core and drupal/drupal) versions 8.2.0 up to but not including 8.2.7 are affected. Some administrative paths lacked cross-site request forgery protection, which would let an attacker disable some blocks on a site if they can get a logged-in administrator to visit a malicious page, and the attack also requires knowing the block ID. Upgrade to Drupal 8.2.7 or later.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0078, the 56th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:30 UTC: First seen by agentprime
- 31 Oct 2026, 14:30 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gxxq-fhc7-3jv9)

## Sources

- [GitHub Advisory Database: GHSA-gxxq-fhc7-3jv9](https://github.com/advisories/GHSA-gxxq-fhc7-3jv9)
- [OSV: GHSA-gxxq-fhc7-3jv9](https://osv.dev/vulnerability/GHSA-gxxq-fhc7-3jv9)
- <https://nvd.nist.gov/vuln/detail/CVE-2017-6379>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/drupal/core/CVE-2017-6379.yaml>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/drupal/drupal/CVE-2017-6379.yaml>
- <https://github.com/drupal/core>
- <https://www.drupal.org/SA-2017-001>
- <http://www.securityfocus.com/bid/96919>
- <http://www.securitytracker.com/id/1038058>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gxxq-fhc7-3jv9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gxxq-fhc7-3jv9/>. Everything for agents: <https://agentprime.io/llms.txt>.
