CVE-2024-45293: XML External Entity Reference (XXE) in PHPSpreadsheet's XLSX reader

Published Oct 7, 2024
·
Updated

Summary The security scanner responsible for preventing XXE attacks in the XLSX reader can be bypassed by slightly modifying the XML structure, utilizing white-spaces. On servers that allow users to upload their own Excel (XLSX) sheets, Server files and sensitive information can be disclosed by providing a crafted sheet.

Details The security scan function in src/PhpSpreadsheet/Reader/Security/XmlScanner.php contains a flawed XML encoding check to retrieve the input file's XML encoding in the toUtf8 function.

The function searches for the XML encoding through a defined regex which looks for encoding="" and/or encoding='', if not found, it defaults to the UTF-8 encoding which bypasses the conversion logic.

$patterns = [ '/encoding="([^"]]?)"/', "/encoding='([^']?)'/", ];

This logic can be used to pass a UTF-7 encoded XXE payload, by utilizing a whitespace before or after the = in the attribute definition.

PoC

Needed: - An Excel sheet (XLSX) with at least one cell containing a value.

Unzip the excel sheet, and modify the xl/SharedStrings.xml file with the following value (note the space after encoding=):

<?xml version="1.0" encoding= 'UTF-7' standalone="yes"?> +ADw-!DOCTYPE abc [ ... ]>

Step-by-step

1. First off, the following string is encoded in base64:

<!ENTITY internal 'abc' >"

Resulting in:

PCFFTlRJVFkgaW50ZXJuYWwgJ2FiYycgID4K

2. The string is used with a parameter entity and the PHP filter wrapper to ultimately define custom entities and call them within the XML.

<?xml version="1.0" encoding= 'UTF-7' standalone="yes"?> +ADw-!DOCTYPE foo [ <!ENTITY % xxe SYSTEM "php://filter//resource=data://text/plain;base64,PCFFTlRJVFkgaW50ZXJuYWwgJ2FiYycgID4K" > %xxe;]> <sst xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" count="1" uniqueCount="1"><si><t>&internal;</t></si></sst>

When this file is parsed by the library, the value abc should be in the original filled cell.

With the help of the PHP filter wrapper, this can be escalated to information disclosure/file read.

Impact Sensitive information disclosure through the XXE on sites that allow users to upload their own excel spreadsheets, and parse them using PHPSpreadsheet's Excel parser.

Other sources

PHPSpreadsheet is a pure PHP library for reading and writing spreadsheet files. The security scanner responsible for preventing XXE attacks in the XLSX reader can be bypassed by slightly modifying the XML structure, utilizing white-spaces. On servers that allow users to upload their own Excel (XLSX) sheets, Server files and sensitive information can be disclosed by providing a crafted sheet. The security scan function in src/PhpSpreadsheet/Reader/Security/XmlScanner.php contains a flawed XML encoding check to retrieve the input file's XML encoding in the toUtf8 function. The function searches for the XML encoding through a defined regex which looks for encoding="" and/or encoding='', if not found, it defaults to the UTF-8 encoding which bypasses the conversion logic. This logic can be used to pass a UTF-7 encoded XXE payload, by utilizing a whitespace before or after the = in the attribute definition. Sensitive information disclosure through the XXE on sites that allow users to upload their own excel spreadsheets, and parse them using PHPSpreadsheet's Excel parser. This issue has been addressed in release versions 1.29.1, 2.1.1, and 2.3.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.

MITRE

Affected Software

7 affected componentsFixes available
composer/phpoffice/phpexcel<=1.8.2
composer/phpoffice/phpspreadsheet>=2.0.0<2.1.1
2.1.1
composer/phpoffice/phpspreadsheet<1.29.1
1.29.1
composer/phpoffice/phpspreadsheet>=2.2.0<2.3.0
2.3.0
PHPOffice phpspreadsheet<1.29.1
PHPOffice phpspreadsheet>=2.0.0<2.1.1
PHPOffice phpspreadsheet>=2.2.0<2.3.0

Event History

Oct 7, 2024
Advisory Published
via GitHub·03:58 PM
CVE Published
via MITRE·08:03 PM
Data Sourced
via MITRE·08:03 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-45293?

CVE-2024-45293 is classified as a high severity vulnerability due to its potential for bypassing XML External Entity (XXE) protections.

2

How do I fix CVE-2024-45293?

To fix CVE-2024-45293, you should update to version 2.1.1 or higher of the phpoffice/phpspreadsheet package.

3

Which versions of phpoffice/phpspreadsheet are affected by CVE-2024-45293?

CVE-2024-45293 affects phpoffice/phpspreadsheet versions prior to 1.29.1 and any versions between 2.0.0 and 2.1.1, as well as between 2.2.0 and 2.3.0.

4

Can CVE-2024-45293 impact file uploads from users?

Yes, CVE-2024-45293 can impact servers that allow users to upload XLSX files, potentially exposing sensitive information.

5

Is CVE-2024-45293 specific to any particular file format?

CVE-2024-45293 specifically affects the XLSX file format due to its XML structure, making it vulnerable to XXE attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203