{"items":[{"id":"NVI-00002352","kind":"vulnerability","title":"XXE in PHPSpreadsheet's XLSX reader","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7cc9-j4mv-vcjp","CVE-2024-48917"],"plain_summary":"OSV carries this publisher advisory for phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpexcel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.29.4 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.3 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.4.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0a72a79e6facdfff4556129d7006362e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T07:59:02.040Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-27441249ca45c69b1e824814c271c7f8"},{"kind":"CVSS","as_of":"2026-06-17T07:59:02.040Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-27441249ca45c69b1e824814c271c7f8"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.728%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54194. Missing scores are unknown.","source_id":"sr-0a72a79e6facdfff4556129d7006362e"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c7295e542511a29694f37a5930a410","url":"https://github.com/advisories/GHSA-7cc9-j4mv-vcjp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7cc9-j4mv-vcjp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.948Z"},{"id":"sr-27441249ca45c69b1e824814c271c7f8","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-48917","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-48917","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:43.945Z"},{"id":"sr-0a72a79e6facdfff4556129d7006362e","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-48917","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.255Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.4"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.3"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.2"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.4.0"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-11-02T20:21:07.842Z","source_updated_at":"2025-03-06T18:38:25.210Z","source_disclosed_at":"2024-11-18T20:01:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.948Z"},{"id":"NVI-00002352","kind":"vulnerability","title":"XXE in PHPSpreadsheet's XLSX reader","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7cc9-j4mv-vcjp","CVE-2024-48917"],"plain_summary":"OSV carries this publisher advisory for phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpexcel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.29.4 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.3 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.4.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-06fd423554d0d8d0397631a6fcec6790"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T07:59:02.040Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-27441249ca45c69b1e824814c271c7f8"},{"kind":"CVSS","as_of":"2026-06-17T07:59:02.040Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-27441249ca45c69b1e824814c271c7f8"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.728%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54197. Missing scores are unknown.","source_id":"sr-06fd423554d0d8d0397631a6fcec6790"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c7295e542511a29694f37a5930a410","url":"https://github.com/advisories/GHSA-7cc9-j4mv-vcjp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7cc9-j4mv-vcjp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.948Z"},{"id":"sr-27441249ca45c69b1e824814c271c7f8","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-48917","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-48917","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:43.945Z"},{"id":"sr-06fd423554d0d8d0397631a6fcec6790","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-48917","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.369Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.4"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.3"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.2"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.4.0"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-11-01T01:04:01.272Z","source_updated_at":"2025-03-06T18:38:25.210Z","source_disclosed_at":"2024-11-18T20:01:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:59.948Z"},{"id":"NVI-00002352","kind":"vulnerability","title":"XXE in PHPSpreadsheet's XLSX reader","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-7cc9-j4mv-vcjp","CVE-2024-48917"],"plain_summary":"OSV carries this publisher advisory for phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpexcel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.29.4 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.3 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.4.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-06fd423554d0d8d0397631a6fcec6790"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.728%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54197. Missing scores are unknown.","source_id":"sr-06fd423554d0d8d0397631a6fcec6790"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c7295e542511a29694f37a5930a410","url":"https://github.com/advisories/GHSA-7cc9-j4mv-vcjp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7cc9-j4mv-vcjp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.948Z"},{"id":"sr-06fd423554d0d8d0397631a6fcec6790","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-48917","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.369Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.4"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.3"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.2"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.4.0"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-10-31T22:13:44.222Z","source_updated_at":"2025-03-06T18:38:25.210Z","source_disclosed_at":"2024-11-18T20:01:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.948Z"},{"id":"NVI-00002352","kind":"vulnerability","title":"XXE in PHPSpreadsheet's XLSX reader","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-7cc9-j4mv-vcjp","CVE-2024-48917"],"plain_summary":"OSV carries this publisher advisory for phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpspreadsheet, phpoffice/phpexcel. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 1.29.4 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.1.3 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.4.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-14c7295e542511a29694f37a5930a410","url":"https://github.com/advisories/GHSA-7cc9-j4mv-vcjp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7cc9-j4mv-vcjp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.948Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.4"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.3"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.2"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.4.0"]},{"certainty":"source_listed","source_ids":["sr-14c7295e542511a29694f37a5930a410"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nThe XmlScanner class has a scan method which should prevent XXE attacks.\n\nHowever, 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: \n\n```\n $patterns = [\n            '/encoding\\\\s*=\\\\s*\"([^\"]*]?)\"/',\n            \"/encoding\\\\s*=\\\\s*'([^']*?)'/\",\n        ];\n``` \n\nA payload for the `workbook.xml` file can for example be created with [CyberChef](https://gc","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-10-31T22:00:33.877Z","source_updated_at":"2025-03-06T18:38:25.210Z","source_disclosed_at":"2024-11-18T20:01:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:59.948Z"}],"next_cursor":null,"snapshot_revision":"42594"}