{"items":[{"id":"NVI-00004543","kind":"vulnerability","title":"PhpSpreadsheet allows absolute path traversal and Server-Side Request Forgery in HTML writer when embedding images is enabled","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-w9xv-qf98-ccq4","CVE-2024-45291"],"plain_summary":"OSV carries this publisher advisory for 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 2.3.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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 1.29.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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.1 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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-02f0ae201a4b2dd98817635d6e7b259d"],"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:53:57.777Z","value":"6.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-ae489257e23b3af9561308880d0a94c6"},{"kind":"CVSS","as_of":"2026-06-17T07:53:57.777Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-ae489257e23b3af9561308880d0a94c6"},{"kind":"EPSS","as_of":"2026-11-06T12:00:23.000Z","value":"0.864%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.58801. Missing scores are unknown.","source_id":"sr-02f0ae201a4b2dd98817635d6e7b259d"}],"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-6a5863f13920f4956921b46aca1652a9","url":"https://github.com/advisories/GHSA-w9xv-qf98-ccq4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xv-qf98-ccq4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-ae489257e23b3af9561308880d0a94c6","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45291","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-45291","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:36.384Z"},{"id":"sr-02f0ae201a4b2dd98817635d6e7b259d","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-45291","publisher":"FIRST EPSS","observed_at":"2026-11-06T20:58:43.503Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.0"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.1"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-11-07T22:29:26.087Z","source_updated_at":"2026-02-04T03:35:21.693Z","source_disclosed_at":"2024-10-07T15:58:06.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:42:41.386Z"},{"id":"NVI-00004543","kind":"vulnerability","title":"PhpSpreadsheet allows absolute path traversal and Server-Side Request Forgery in HTML writer when embedding images is enabled","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-w9xv-qf98-ccq4","CVE-2024-45291"],"plain_summary":"OSV carries this publisher advisory for 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 2.3.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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 1.29.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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.1 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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-11a78962ea55d82811e224175f805fab"],"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:53:57.777Z","value":"6.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-ae489257e23b3af9561308880d0a94c6"},{"kind":"CVSS","as_of":"2026-06-17T07:53:57.777Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-ae489257e23b3af9561308880d0a94c6"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.864%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.58642. Missing scores are unknown.","source_id":"sr-11a78962ea55d82811e224175f805fab"}],"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-6a5863f13920f4956921b46aca1652a9","url":"https://github.com/advisories/GHSA-w9xv-qf98-ccq4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xv-qf98-ccq4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-ae489257e23b3af9561308880d0a94c6","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45291","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-45291","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:36.384Z"},{"id":"sr-11a78962ea55d82811e224175f805fab","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-45291","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.254Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.0"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.1"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-11-06T15:18:17.679Z","source_updated_at":"2026-02-04T03:35:21.693Z","source_disclosed_at":"2024-10-07T15:58:06.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:42:41.386Z"},{"id":"NVI-00004543","kind":"vulnerability","title":"PhpSpreadsheet allows absolute path traversal and Server-Side Request Forgery in HTML writer when embedding images is enabled","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-w9xv-qf98-ccq4","CVE-2024-45291"],"plain_summary":"OSV carries this publisher advisory for 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 2.3.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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 1.29.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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.1 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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-11a78962ea55d82811e224175f805fab"],"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-11-01T12:00:16.000Z","value":"0.864%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.58642. Missing scores are unknown.","source_id":"sr-11a78962ea55d82811e224175f805fab"}],"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-6a5863f13920f4956921b46aca1652a9","url":"https://github.com/advisories/GHSA-w9xv-qf98-ccq4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xv-qf98-ccq4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-11a78962ea55d82811e224175f805fab","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-45291","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.254Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.0"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.1"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-11-03T17:49:18.473Z","source_updated_at":"2026-02-04T03:35:21.693Z","source_disclosed_at":"2024-10-07T15:58:06.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:42:41.386Z"},{"id":"NVI-00004543","kind":"vulnerability","title":"PhpSpreadsheet allows absolute path traversal and Server-Side Request Forgery in HTML writer when embedding images is enabled","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-w9xv-qf98-ccq4","CVE-2024-45291"],"plain_summary":"OSV carries this publisher advisory for 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 2.3.0 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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 1.29.2 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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.1 for phpoffice/phpspreadsheet. Confirm the publisher’s latest guidance.","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"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-6a5863f13920f4956921b46aca1652a9","url":"https://github.com/advisories/GHSA-w9xv-qf98-ccq4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xv-qf98-ccq4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.3.0"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpspreadsheet","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.1.1"]},{"certainty":"source_listed","source_ids":["sr-6a5863f13920f4956921b46aca1652a9"],"technology":"phpoffice/phpexcel","known_exclusions":[],"conditions_summary":"### Summary\n\nIt's possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer->setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file's type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.\n\n### Details\n\nXLSX files allow embedding or linking media. When \n\nIn `xl/drawings/drawing1.xml` an attacker can do e.g.:\n```xml\n\n```\n\nAnd then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:\n```xml\n\n```\nor\n```xml\n\n```\n\nWhen the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.\n\n```php\nif ($this->embedI","public_affected_ranges":["ECOSYSTEM: introduced 0; last_affected 1.8.2"]}],"null_published_at":"2026-10-31T22:12:57.131Z","source_updated_at":"2026-02-04T03:35:21.693Z","source_disclosed_at":"2024-10-07T15:58:06.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:42:41.386Z"}],"next_cursor":null,"snapshot_revision":"42594"}