CVE-2018-1000820: XML External Entity (XXE) vulnerability in org.neo4j.procedure:apoc

org.neo4j.procedure:apoc Updated 02 Oct 2025

Summary

20/12/2018
Yes i
Critical
10.0

CVE-2018-1000820: XML External Entity (XXE) vulnerability in neo4j.procedure:apoc. Affects org.neo4j.procedure:apoc versions < 3.4.0.4. Fixed in 3.4.0.4. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

org.neo4j.procedure:apoc is a Maven package that provides additional procedures for Neo4j, a graph database management system. These procedures enhance the functionality of Neo4j by adding new capabilities. However, versions of neo4j-apoc-procedures prior to commit 45bc09c are vulnerable to an XML External Entity (XXE) vulnerability in the XML Parser. This vulnerability can lead to the disclosure of confidential data, denial of service, SSRF, and port scanning.

Vulnerability Detail

The XML External Entity (XXE) vulnerability in org.neo4j.procedure:apoc allows an attacker to exploit the XML Parser, potentially resulting in the disclosure of sensitive information, denial of service attacks, server-side request forgery (SSRF), and port scanning. This vulnerability has a CVSS score of 10.0, indicating its critical severity. It has been fixed in versions after commit 45bc09c.

How To Fix

Latest published version: 4.4.0.40 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.4.0.4

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to a fixed version of org.neo4j.procedure:apoc to mitigate the risk.

Conclusion

The XML External Entity (XXE) vulnerability in org.neo4j.procedure:apoc poses a significant risk to the security and functionality of the affected application. It is crucial to update to a fixed version of the package (3.4.0.4 or later) to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.neo4j.procedure:apoc →

Share this vulnerability

FAQ

org.neo4j.procedure:apoc is a Maven package that provides additional procedures for Neo4j, a graph database management system. These procedures enhance the functionality of Neo4j by adding new capabilities.

An XML External Entity (XXE) vulnerability is a type of security vulnerability that allows an attacker to exploit an XML parser by including external entities or files. This can lead to the disclosure of sensitive information, denial of service attacks, server-side request forgery (SSRF), and port scanning.

The potential consequences of this vulnerability include the disclosure of confidential data, denial of service attacks, server-side request forgery (SSRF), and port scanning. These can have severe impacts on the security and functionality of the affected application.

To fix this vulnerability, update the org.neo4j.procedure:apoc package to version 3.4.0.4 or later. This can be done by updating the package version in the project's Maven configuration file (pom.xml) and rebuilding the project.

No, there is no known workaround for this vulnerability. It is crucial to update to a fixed version of org.neo4j.procedure:apoc to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for org.neo4j.procedure:apoc.

How To Fix

Latest published version: 4.4.0.40 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.4.0.4

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback