# CVE-2016-5000: Apache POI's XLSX2CSV Example XML External Entity (XXE) Vulnerability

> Remote attackers can read arbitrary files via crafted OpenXML documents exploiting an XML External Entity vulnerability in the XLSX2CSV example.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-5000, GHSA-pmqq-7wfv-jfff, UBUNTU-CVE-2016-5000

## What is CVE-2016-5000?

CVE-2016-5000 is a medium-severity vulnerability in n/a, published on 5 Aug 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

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

## Which versions are affected by CVE-2016-5000?

2 open source packages ship an affected version, including org.apache.poi:poi-examples. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.poi:poi-examples` | Maven | All versions | 3.14 |
| `org.apache.poi:poi-examples` | Maven | All versions | 3.14 |

Products: Apache Poi.

## How do I fix CVE-2016-5000?

Upgrade org.apache.poi:poi-examples to 3.14 or later.

## Is CVE-2016-5000 being exploited?

There is no known exploitation of CVE-2016-5000 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-12626](https://insights.sbomify.com/CVE-2017-12626/): Denial of Service in Apache POI (high 7.5)
- [CVE-2022-26336](https://insights.sbomify.com/CVE-2022-26336/): A carefully crafted TNEF file can cause an out of memory exception (medium 5.5)
- [CVE-2019-12415](https://insights.sbomify.com/CVE-2019-12415/): Improper Restriction of XML External Entity Reference in Apache POI (medium 5.5)
- [CVE-2017-5644](https://insights.sbomify.com/CVE-2017-5644/): Improper Restriction of Recursive Entity References in DTDs in Apache POI (medium 5.5)
- [CVE-2025-31672](https://insights.sbomify.com/CVE-2025-31672/): Apache POI OOXML Vulnerable to Improper Input Validation in OOXML File Parsing (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5000 and fix it if it is affected.

What it is: CVE-2016-5000 is a medium-severity vulnerability in n/a, published on 5 Aug 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-5000 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.poi:poi-examples (Maven): affected all versions; fixed in 3.14
- org.apache.poi:poi-examples (Maven): affected all versions; fixed in 3.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-5000/ (Markdown: https://insights.sbomify.com/CVE-2016-5000/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-5000
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-5000
- OSV: https://osv.dev/vulnerability/CVE-2016-5000

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-5000/
Summaries are generated and may contain mistakes; the official description above is the record.