CVE-2013-7259: Neo4J vulnerable to Cross-Site Request Forgery

CVE-2013-7259 · Severity: medium · CVSS 4 · Published 2022-05-17

Neo4J vulnerable to Cross-Site Request Forgery

Technologies: org.neo4j:neo4j (Maven). Vendors: Maven.

Quick answers

Is CVE-2013-7259 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-7259 being exploited in the wild.
How severe is CVE-2013-7259?
Medium severity, with a CVSS score of 4, published 17 May 2022.
Which products and versions are affected?
org.neo4j:neo4j (Maven) ECOSYSTEM:introduced=0,fixed=2.2.0-M01.
Is there a fix for CVE-2013-7259?
Yes. org.neo4j:neo4j (Maven): upgrade to 2.2.0-M01 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-7259?
Check whether you run org.neo4j:neo4j (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.neo4j:neo4j (Maven): upgrade to 2.2.0-M01 or later
    # set org.neo4j:neo4j to 2.2.0-M01 in your pom.xml or build.gradle

Affected products

  • org.neo4j:neo4j (Maven) ECOSYSTEM:introduced=0,fixed=2.2.0-M01

Identifiers

  • CVE-2013-7259
  • GHSA-x626-q4v7-7xc6

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.