CVE-2024-45060

PhpSpreadsheet has an Unauthenticated Cross-Site-Scripting (XSS) in sample file

The impact of this vulnerability on the project is expected to be relatively low since these are sample files that should not be included when the library is used properly (e.g., through composer). However, at least two instances of popular WordPress plugins have unintentionally exposed this file by including the entire git repository. Since these files also serve as reference points for developers using the library, addressing this issue can enhance security for users.

A solution to fix the vulnerability is proposed below, and a request for a CVE assignment has been made to facilitate responsible disclosure of the security issue to the affected WordPress plugins.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-45060 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.0, 1.29.2, 2.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

A quick and easy solution to prevent this attack is to force the parameters to be numerical values:

if (isset($_POST['submit'])) {
    $_POST['A'] = floatval($_POST['A']);
    $_POST['B'] = floatval($_POST['B']);
    $_POST['C'] = floatval($_POST['C']);
    if ($_POST['A'] == 0) {

Thank you for your time!

1. What is CVE-2024-45060? CVE-2024-45060 is a medium-severity cross-site scripting (XSS) vulnerability in phpoffice/phpspreadsheet (composer), affecting versions >= 2.2.0, < 2.3.0. It is fixed in 2.3.0, 1.29.2, 2.1.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-45060? CVE-2024-45060 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-45060?
   • phpoffice/phpspreadsheet (composer) (versions >= 2.2.0, < 2.3.0)
   • phpoffice/phpexcel (composer) (versions <= 1.8.2)
4. Is there a fix for CVE-2024-45060? Yes. CVE-2024-45060 is fixed in 2.3.0, 1.29.2, 2.1.1. Upgrade to this version or later.
5. Is CVE-2024-45060 exploitable, and should I be worried? Whether CVE-2024-45060 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-45060 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-45060?
   • Upgrade phpoffice/phpspreadsheet to 2.3.0 or later
   • Upgrade phpoffice/phpspreadsheet to 1.29.2 or later
   • Upgrade phpoffice/phpspreadsheet to 2.1.1 or later