CVE-2019-5312

CRITICALNVD 9.89.8—

9.8

An issue was discovered in weixin-java-tools v3.3.0. There is an XXE vulnerability in the getXmlDoc method of the BaseWxPayResult.java file. NOTE: this issue exists because of an incomplete fix for CVE-2018-20318.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 59.5%
KEV: Not listed

Published

January 4, 2019

Last Modified

September 12, 2025

Advisory Details (1)

Auto-updated Jun 2, 2026

No patch confirmed yet.

generic

XXE Vulnerability · Issue #903 · binarywang/WxJava · GitHub

https://github.com/Wechat-Group/WxJava/issues/903

Affected Packages

(1 across 1 ecosystem)

Maven(1)

Package	Vulnerable range	Fixed in	Dependents
com.github.binarywang:weixin-java-common	1.3.4 ... 3.3.1.B (129 versions)	3.3.2.B	—

Weakness Classification(1)

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

CWE-611Improper Restriction of XML External Entity Reference (XXE)

Data Freshness Timeline

(refreshed 11× in last 7d / 19× 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-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 23:43 UTCEG score recompute
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 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
2026-05-24 16:47 UTCepss_batch

Frequently asked(5)

What is CVE-2019-5312?

CVE-2019-5312 is a critical vulnerability published on January 4, 2019. An issue was discovered in weixin-java-tools v3.3.0. There is an XXE vulnerability in the getXmlDoc method of the BaseWxPayResult.java file. NOTE: this issue exists because of an incomplete fix for CVE-2018-20318.

When was CVE-2019-5312 disclosed?

CVE-2019-5312 was first published in the National Vulnerability Database on January 4, 2019, with the most recent update on September 12, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-5312 actively exploited?

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

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

CVE-2019-5312 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2019-5312?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-5312, 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-5312

Explore →

Is Your Infrastructure Affected by CVE-2019-5312?

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

Start Free Scan →Browse All CVEs