CVE-2019-12415· NVD / CVE Program· CNA apache

In Apache POI up to 4.1.0, when using the tool XSSFExportToXml to convert user-provided Microsoft Excel documents, a specially crafted docum

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.99% (FIRST EPSS); higher than 62.1% of all records.
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: libapache-poi-java (Debian:14) 4.1.1-1; org.apache.poi:poi (Maven) 4.1.1.
Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to libapache-poi-java (Debian:14) 4.1.1-1; org.apache.poi:poi (Maven) 4.1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Apache POI up to 4.1.0, when using the tool XSSFExportToXml to convert user-provided Microsoft Excel documents, a specially crafted document can allow an attacker to read files from the local filesystem or from internal network resources via XML External Entity (XXE) Processing.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Published: Oct 23, 2019
Updated: Jun 16, 2026
EPSS: 0.9% · 62th percentile
CWE: CWE-611

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.9%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	poi	cpe:2.3:a:apache:poi
oracle	application testing suite	cpe:2.3:a:oracle:application_testing_suite
oracle	banking enterprise originations	cpe:2.3:a:oracle:banking_enterprise_originations
oracle	banking enterprise product manufacturing	cpe:2.3:a:oracle:banking_enterprise_product_manufacturing
oracle	banking payments	cpe:2.3:a:oracle:banking_payments
oracle	banking platform	cpe:2.3:a:oracle:banking_platform
oracle	big data discovery	cpe:2.3:a:oracle:big_data_discovery
oracle	communications diameter signaling router idih\	cpe:2.3:a:oracle:communications_diameter_signaling_router_idih\
oracle	endeca information discovery studio	cpe:2.3:a:oracle:endeca_information_discovery_studio
oracle	enterprise manager base platform	cpe:2.3:a:oracle:enterprise_manager_base_platform
oracle	enterprise repository	cpe:2.3:a:oracle:enterprise_repository
oracle	financial services analytical applications infrastructure	cpe:2.3:a:oracle:financial_services_analytical_applications_infrastructure

and 15 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache poiup to 4.1.0 inclusive
oracle application testing suite12.5.0.3
oracle application testing suite13.1.0.1
oracle application testing suite13.2.0.1
oracle application testing suite13.3.0.1
oracle banking enterprise originations2.7.0
oracle banking enterprise originations2.8.0
oracle banking enterprise product manufacturing2.7.0
oracle banking enterprise product manufacturing2.8.0
oracle banking payments14.0.0
oracle banking payments14.1.0
oracle banking platform2.4.0
oracle banking platform2.4.1
oracle banking platform2.5.0
oracle banking platform2.6.0
oracle banking platform2.6.1
oracle banking platform2.6.2
oracle banking platform2.7.0
oracle banking platform2.7.1
oracle banking platform2.9.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

n/a Apache POI
- Apache POI up to 4.1.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	libapache-poi-java	all versions	—
Debian:14	libapache-poi-java	before 4.1.1-1	4.1.1-1
Maven	org.apache.poi:poi	before 4.1.1	4.1.1

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2017-12626Apache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks: 1) Infinite Loops while parsing crafted WMF, EMF,
33Monitor
CVE-2017-5644Apache POI in versions prior to release 3.15 allows remote attackers to cause a denial of service (CPU consumption) via a specially crafted
23Monitor
CVE-2016-5000The XLSX2CSV example in Apache POI before 3.14 allows remote attackers to read arbitrary files via a crafted OpenXML document containing an
23Monitor
CVE-2022-26336A carefully crafted TNEF file can cause an out of memory exception
22Monitor
CVE-2014-9527HSLFSlideShow in Apache POI before 3.11 allows remote attackers to cause a denial of service (infinite loop and deadlock) via a crafted PPT
22Monitor
CVE-2012-0213The UnhandledDataStructure function in hwpf/model/UnhandledDataStructure.java in Apache POI 3.8 and earlier allows remote attackers to cause
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:libapache-poi-java	4.1.1-1 · Debian:14	Package registry (OSV)
Maven:org.apache.poi:poi	4.1.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).