CVE•Published 2020-05-01•Modified 2026-08-25•1 article on news•6 live references•NVD data

CVE-2020-10683Dom4j_project · Dom4j

Vulnerability data via NVD (ingested)

CVSS v3.1

9.8

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS percentile

Exploit Prediction Scoring System · top 6% of all CVEs

Weaknesses (CWE)

CWE-611Improper Restriction of XML External Entity Reference

Description

dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.

Timeline

Published 2020-05-01

Modified 2026-08-25

External references

NVD MITRE Exploit-DB GitHub PoC trickest/cve VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag40 hosts

vuln:CVE-2020-10683

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Dom4j Project Dom4j"

All exposed Dom4j Project Dom4j instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Dom4j"

HTTP body or banner mentions "Dom4j" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2020-10683