Advisory record · GHSA-x626-q4v7-7xc6

Neo4J vulnerable to Cross-Site Request Forgery

CVSS 4.0, no score publishedEPSS 0.013 · 69th percentile

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.

PackageEcosystemAffectedFixed in
org.neo4j:neo4jMaven<2.2.0-M012.2.0-M01
Identifiers
GHSA-x626-q4v7-7xc6 · CVE-2013-7259
Weakness (CWE)
CWE-78 · CWE-352
Published
17 May 2022
Updated
14 Apr 2025

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

ScoreRatingCVSSVectorSource
Not published None 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 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

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

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.