PHPExcel vulnerable to XXE attacks through libxml

published 2014-06-04 12y ago modified 2026-06-17 4mo ago also GHSA-28rm-rj57-qjpv , EUVD-2022-1943

cvss: 7.5; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

PHPExcel before 1.8.0, as used in ownCloud Server before 5.0.15 and 6.0.x before 6.0.2, does not disable external entity loading in libxml, which allows remote attackers to read arbitrary files, cause a denial of service, or possibly have other impact via an XML External Entity (XXE) attack.

Patch / fix

fixed in 1 links 1

packagist phpoffice/phpexcel 1.8.0

github.com/PHPOffice/PHPExcel@e04bf7e commit

Is CVE-2014-2054 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem	package	affected	fixed in
packagist	phpoffice/phpexcel	<1.8.0	1.8.0

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

CVE List CVE-2014-2054
GitHub Advisory GHSA-28rm-rj57-qjpv
NVD CVE-2014-2054

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.