Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2013-7259: Multiple cross-site request forgery (CSRF) vulnerabilities in Neo4J 1.9.2 allow remote attackers to hijack the authentication of…

MediumCVSS 6.8 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.9% of all records.
  • Fixed version: org.neo4j:neo4j (Maven) 2.2.0-M01.

Low priority for now. Upgrade to org.neo4j:neo4j (Maven) 2.2.0-M01 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Multiple cross-site request forgery (CSRF) vulnerabilities in Neo4J 1.9.2 allow remote attackers to hijack the authentication of administrators for requests that execute arbitrary code, as demonstrated by a request to (1) db/data/ext/GremlinPlugin/graphdb/execute_script or (2) db/manage/server/console/.

Published
Apr 29, 2014
Updated
Jun 16, 2026
EPSS
1.2% · 69th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2013-7259

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
neo4jneo4j

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • neo4j neo4j1.9.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.neo4j:neo4jbefore 2.2.0-M012.2.0-M01

Other highest-scoring records for the same primary product.

  • CVE-2021-34371Neo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that arbitrarily deserializes Java objects, e.g., through…
    43Plan
  • CVE-2018-18389Due to incorrect access control in Neo4j Enterprise Database Server 3.4.x before 3.4.9, the setting of LDAP for authentication with…
    40Plan
  • CVE-2024-34517The Cypher component in Neo4j 5.0.0 through 5.18 mishandles IMMUTABLE privileges in some situations where an attacker already has admin…
    26Monitor

Published before and after this one in the same product

  • Later →CVE-2026-1337Feb 6, 2026 · Insufficient escaping of unicode characters in query log
    4Monitor
  • Later →CVE-2026-1497Mar 11, 2026 · Incorrect privilege assignment in composite databases
    8Monitor
  • Later →CVE-2026-1471Mar 11, 2026 · Caching of authentication context
    8Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.neo4j:neo4j2.2.0-M01Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    P

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:P/A:P

    nvd-primary

    Root cause

    User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    const host = req.body.host;exec("ping -c 1 " + host, onResult);

    Fixed

    ts
    const host = req.body.host;if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);execFile("ping", ["-c", "1", host], onResult);

    References

    All records