Skip to content

GHSA-7cc9-j4mv-vcjp CVE-2024-48917

XXE in PHPSpreadsheet's XLSX reader

High Packagist
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.73%
Chance of exploitation in the next 30 days. Higher than 54.19% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-611 Improper Restriction of XML External Entity Reference
Fix
1.29.4
Upgrade phpoffice/phpspreadsheet to this version or later

Description

Summary

The XmlScanner class has a scan method which should prevent XXE attacks.

However, we found another bypass than the previously reported CVE-2024-47873, the regexes from the findCharSet method, which is used for determining the current encoding can be bypassed by using a payload in the encoding UTF-7, and adding at end of the file a comment with the value encoding="UTF-8" with ", which is matched by the first regex, so that encoding='UTF-7' with single quotes ' in the XML header is not matched by the second regex:

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

A payload for the workbook.xml file can for example be created with CyberChef. If you open an Excel file containing the payload from the link above stored in the workbook.xml file with PhpSpreadsheet, you will receive an HTTP request on 127.0.0.1:12345. You can test that an HTTP request is created by running the nc -nlvp 12345 command before opening the file containing the payload with PhpSpreadsheet.

To create the payload you need:

  1. Create a file containing <?xml version = "1.0" encoding='UTF-7' in an XML file
  2. Use the link attached above to create your XXE payload and add it to the XML file.
  3. Add +ADw-+ACE---encoding="UTF-8"--+AD4- to the end of the XML file, which is matched by the first regex.

PoC

payload.xlsx

  • Create a new folder.
  • Run the composer require phpoffice/phpspreadsheet command in the new folder.
  • Create an index.php file in that folder with the following content:
<?php
require 'vendor/autoload.php';

use PhpOffice\PhpSpreadsheet\Spreadsheet;
use PhpOffice\PhpSpreadsheet\Writer\Xlsx;

$spreadsheet = new Spreadsheet();

$inputFileType = 'Xlsx';
$inputFileName = './payload.xlsx';

/**  Create a new Reader of the type defined in $inputFileType  **/
$reader = \PhpOffice\PhpSpreadsheet\IOFactory::createReader($inputFileType);
/**  Advise the Reader that we only want to load cell data  **/
$reader->setReadDataOnly(true);

$worksheetData = $reader->listWorksheetInfo($inputFileName);

foreach ($worksheetData as $worksheet) {

$sheetName = $worksheet['worksheetName'];

echo "<h4>$sheetName</h4>";
/**  Load $inputFileName to a Spreadsheet Object  **/
$reader->setLoadSheetsOnly($sheetName);
$spreadsheet = $reader->load($inputFileName);

$worksheet = $spreadsheet->getActiveSheet();
print_r($worksheet->toArray());

}

Impact

An attacker can bypass the sanitizer and achieve an XXE attack.

Affected versions

Packagist

PackageVulnerableFixed in
phpoffice/phpexcel
<= 1.8.2
No fix yet
phpoffice/phpspreadsheet
< 1.29.4
1.29.4
phpoffice/phpspreadsheet
>= 2.0.0, < 2.1.3
2.1.3
phpoffice/phpspreadsheet
>= 2.2.0, < 2.3.2
2.3.2
phpoffice/phpspreadsheet
>= 3.3.0, < 3.4.0
3.4.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

phpoffice/phpspreadsheet Packagist → 1.29.4

composer
composer require phpoffice/phpspreadsheet:^1.29.4

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-611: Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How to prevent it
  • Implementation, System Configuration: Many XML parsers and validators can be configured to disable external entity expansion.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-2phh-27fw-q4gc
PhpSpreadsheet: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading
Medium Also affects phpoffice/phpspreadsheet
GHSA-j2w7-387v-m2rq
PhpSpreadsheet ODS Reader: Unbounded number-rows-repeated → CPU & Memory Exhaustion (DoS)
High Also affects phpoffice/phpspreadsheet
GHSA-3x94-m842-937c
PhpSpreadsheet: XmlScanner Bypass via ISO-2022 Escape Sequences Allows XXE and Denial of Service
High Also affects phpoffice/phpspreadsheet
GHSA-rxj4-h86g-25gc
PhpSpreadsheet: XmlScanner Bypass via Double-Encoded unentity() TOCTOU Allows XXE and Denial of Service
High Also affects phpoffice/phpspreadsheet
GHSA-xh5m-36r6-47m3
PHPSpreadsheet: XLS/OLE sector-chain self-loop causes memory exhaustion
High Also affects phpoffice/phpspreadsheet
GHSA-2mrg-gjxq-2gvr
PHPSpreadsheet: Gnumeric reader unbounded gzip expansion causes memory exhaustion
High Also affects phpoffice/phpspreadsheet
GHSA-6hq5-7373-42rg
PHPSpreadsheet: SSRF bypass via HTTP redirect in WEBSERVICE() domain whitelist
High Also affects phpoffice/phpspreadsheet
GHSA-87m4-826x-3crx
PHPSpreadsheet has a patch bypass for CVE-2026-34084
Critical Also affects phpoffice/phpspreadsheet
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor