CVE-2019-20201

MEDIUMNVD 6.56.5—

6.5

An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 61.2%
KEV: Not listed

Published

December 31, 2019

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://sourceforge.net/p/ezxml/bugs/16/
af854a3a-2127-422b-91ae-364da2661108https://sourceforge.net/p/ezxml/bugs/16/

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 09:44 UTCEG score recompute
2026-05-27 09:44 UTCGHSA enrichment
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-20201?

CVE-2019-20201 is a medium vulnerability published on December 31, 2019. An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxmlparse* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.

When was CVE-2019-20201 disclosed?

CVE-2019-20201 was first published in the National Vulnerability Database on December 31, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-20201 actively exploited?

CVE-2019-20201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 61.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-20201?

CVE-2019-20201 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2019-20201?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-20201, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-20201

Explore →

Is Your Infrastructure Affected by CVE-2019-20201?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-20201

📅 Published

🔄 Last Modified

🔗 References (2)