# Neo4J vulnerable to Cross-Site Request Forgery

Advisory record · `GHSA-x626-q4v7-7xc6`

- **Identifiers:** `GHSA-x626-q4v7-7xc6` · `CVE-2013-7259`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html) · [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md) · [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 17 May 2022
- **Updated:** 14 Apr 2025
- **Reviewed by a person:** No

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

## Affected packages

- `org.neo4j:neo4j` (Maven): affected `<2.2.0-M01`; fixed in `2.2.0-M01`

## Machine-written summary

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

> Neo4J (org.neo4j:neo4j) versions before 2.2.0-M01 are vulnerable to cross-site request forgery. A remote attacker can make an authenticated administrator's browser send requests that run arbitrary code on the server, which the source demonstrates against version 1.9.2. Upgrade to 2.2.0-M01 or later.

Written 7 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

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x626-q4v7-7xc6)

## Sources

- [GitHub Advisory Database: GHSA-x626-q4v7-7xc6](https://github.com/advisories/GHSA-x626-q4v7-7xc6)
- [OSV: GHSA-x626-q4v7-7xc6](https://osv.dev/vulnerability/GHSA-x626-q4v7-7xc6)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-7259>
- <https://github.com/neo4j/neo4j/issues/2826>
- <https://github.com/neo4j/neo4j/commit/40ad76078a25666d8b218772b6491fb443020df9>
- <https://github.com/neo4j/neo4j>
- <https://github.com/o2platform/DefCon_RESTing/tree/master/Live-Demos/Neo4j>
- <https://web.archive.org/web/20131017043717/http://blog.diniscruz.com/2013/08/neo4j-csrf-payload-to-start-processes.html>
- <http://www.openwall.com/lists/oss-security/2014/01/03/3>
- <http://www.openwall.com/lists/oss-security/2014/01/03/8>

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-x626-q4v7-7xc6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x626-q4v7-7xc6/>. Everything for agents: <https://agentprime.io/llms.txt>.
