Skip to content
Fencer Intel
medium 5.5

CVE-2016-5000 json

Apache POI's XLSX2CSV Example XML External Entity (XXE) Vulnerability

published 2016-08-05 10 y ago modified 2026-06-17 4 mo ago also GHSA-pmqq-7wfv-jfff , EUVD-2022-4799

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.2%
EPSS 4.2% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

The XLSX2CSV example in Apache POI before 3.14 allows remote attackers to read arbitrary files via a crafted OpenXML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

Patch / fix

  • maven org.apache.poi:poi-examples 3.14

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-5000 updated cvss 7.5

poi: XML External Entity (XXE) Vulnerability in Apache POI's XLSX2CSV Example

  • Red Hat BPM Suite 6 poi poi Red Hat Enterprise Virtualization 3 jasperreports-server-pro Red Hat JBoss BRMS 5 poi poi Red Hat JBoss BRMS 6 poi poi Red Hat JBoss Data Virtualization 6 poi poi Red Hat JBoss Fuse Service Works 6 poi poi
    +1 more products
    Red Hat JBoss Portal 6 poi poi
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.15% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.poi:poi-examples
<3.14
3.14

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.