{"items":[{"id":"NVI-00006482","kind":"vulnerability","title":"php-imap vulnerable to RCE through a directory traversal vulnerability","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-47p7-xfcc-4pv9","CVE-2023-35169"],"plain_summary":"OSV carries this publisher advisory for webklex/php-imap, webklex/laravel-imap. 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 5.3.0 for webklex/php-imap. Confirm the publisher’s latest guidance.","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"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 5.3.0 for webklex/laravel-imap. Confirm the publisher’s latest guidance.","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"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-1494adf5db34bdbb6180cb8fc1986019"],"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-17T06:04:32.600Z","value":"9 CRITICAL (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-37ff7646825ba6007044f5a38ce65fa8"},{"kind":"CVSS","as_of":"2026-06-17T06:04:32.600Z","value":"9.8 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-37ff7646825ba6007044f5a38ce65fa8"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"3.191%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.881. Missing scores are unknown.","source_id":"sr-1494adf5db34bdbb6180cb8fc1986019"}],"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-b6641e8941f5e69f2fc79e99a4362b79","url":"https://github.com/advisories/GHSA-47p7-xfcc-4pv9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-47p7-xfcc-4pv9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.666Z"},{"id":"sr-37ff7646825ba6007044f5a38ce65fa8","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-35169","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-35169","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:44.011Z"},{"id":"sr-1494adf5db34bdbb6180cb8fc1986019","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-2023-35169","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"technology":"webklex/php-imap","known_exclusions":[],"conditions_summary":"### Summary\nAn unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability which results in a remote code execution vulnerability.\n\n### Details\nAn attacker can send an email with a malicious attachment to the inbox, which gets crawled with webklex/php-imap or webklex/laravel-imap. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)` (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L251-L255).\nIn this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L252).\nEven if a developer passes a `$filename` into the `Attachment::save()` method, e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package.\nThere is also no restriction about the file extension (e.g. \".php\") or the contents of a file","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.0"]},{"certainty":"source_listed","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"technology":"webklex/laravel-imap","known_exclusions":[],"conditions_summary":"### Summary\nAn unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability which results in a remote code execution vulnerability.\n\n### Details\nAn attacker can send an email with a malicious attachment to the inbox, which gets crawled with webklex/php-imap or webklex/laravel-imap. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)` (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L251-L255).\nIn this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L252).\nEven if a developer passes a `$filename` into the `Attachment::save()` method, e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package.\nThere is also no restriction about the file extension (e.g. \".php\") or the contents of a file","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.0"]}],"null_published_at":"2026-11-01T01:04:01.283Z","source_updated_at":"2026-09-10T03:50:01.941Z","source_disclosed_at":"2023-06-21T21:58:58.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:49.666Z"},{"id":"NVI-00006482","kind":"vulnerability","title":"php-imap vulnerable to RCE through a directory traversal vulnerability","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-47p7-xfcc-4pv9","CVE-2023-35169"],"plain_summary":"OSV carries this publisher advisory for webklex/php-imap, webklex/laravel-imap. 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 5.3.0 for webklex/php-imap. Confirm the publisher’s latest guidance.","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"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 5.3.0 for webklex/laravel-imap. Confirm the publisher’s latest guidance.","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"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-1494adf5db34bdbb6180cb8fc1986019"],"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":"3.191%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.881. Missing scores are unknown.","source_id":"sr-1494adf5db34bdbb6180cb8fc1986019"}],"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-b6641e8941f5e69f2fc79e99a4362b79","url":"https://github.com/advisories/GHSA-47p7-xfcc-4pv9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-47p7-xfcc-4pv9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.666Z"},{"id":"sr-1494adf5db34bdbb6180cb8fc1986019","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-2023-35169","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"technology":"webklex/php-imap","known_exclusions":[],"conditions_summary":"### Summary\nAn unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability which results in a remote code execution vulnerability.\n\n### Details\nAn attacker can send an email with a malicious attachment to the inbox, which gets crawled with webklex/php-imap or webklex/laravel-imap. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)` (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L251-L255).\nIn this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L252).\nEven if a developer passes a `$filename` into the `Attachment::save()` method, e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package.\nThere is also no restriction about the file extension (e.g. \".php\") or the contents of a file","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.0"]},{"certainty":"source_listed","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"technology":"webklex/laravel-imap","known_exclusions":[],"conditions_summary":"### Summary\nAn unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability which results in a remote code execution vulnerability.\n\n### Details\nAn attacker can send an email with a malicious attachment to the inbox, which gets crawled with webklex/php-imap or webklex/laravel-imap. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)` (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L251-L255).\nIn this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L252).\nEven if a developer passes a `$filename` into the `Attachment::save()` method, e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package.\nThere is also no restriction about the file extension (e.g. \".php\") or the contents of a file","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.0"]}],"null_published_at":"2026-10-31T22:27:06.721Z","source_updated_at":"2026-09-10T03:50:01.941Z","source_disclosed_at":"2023-06-21T21:58:58.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:49.666Z"},{"id":"NVI-00006482","kind":"vulnerability","title":"php-imap vulnerable to RCE through a directory traversal vulnerability","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-47p7-xfcc-4pv9","CVE-2023-35169"],"plain_summary":"OSV carries this publisher advisory for webklex/php-imap, webklex/laravel-imap. 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 5.3.0 for webklex/php-imap. Confirm the publisher’s latest guidance.","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"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 5.3.0 for webklex/laravel-imap. Confirm the publisher’s latest guidance.","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"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-b6641e8941f5e69f2fc79e99a4362b79","url":"https://github.com/advisories/GHSA-47p7-xfcc-4pv9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-47p7-xfcc-4pv9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.666Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"technology":"webklex/php-imap","known_exclusions":[],"conditions_summary":"### Summary\nAn unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability which results in a remote code execution vulnerability.\n\n### Details\nAn attacker can send an email with a malicious attachment to the inbox, which gets crawled with webklex/php-imap or webklex/laravel-imap. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)` (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L251-L255).\nIn this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L252).\nEven if a developer passes a `$filename` into the `Attachment::save()` method, e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package.\nThere is also no restriction about the file extension (e.g. \".php\") or the contents of a file","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.0"]},{"certainty":"source_listed","source_ids":["sr-b6641e8941f5e69f2fc79e99a4362b79"],"technology":"webklex/laravel-imap","known_exclusions":[],"conditions_summary":"### Summary\nAn unsanitized attachment filename allows any unauthenticated user to leverage a directory traversal vulnerability which results in a remote code execution vulnerability.\n\n### Details\nAn attacker can send an email with a malicious attachment to the inbox, which gets crawled with webklex/php-imap or webklex/laravel-imap. Prerequisite for the vulnerability is that the script stores the attachments without providing a `$filename`, or providing an unsanitized `$filename`, in `src/Attachment::save(string $path, string $filename = null)` (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L251-L255).\nIn this case, where no `$filename` gets passed into the `Attachment::save()` method, the package would use a series of unsanitized and insecure input values from the mail as fallback (https://github.com/Webklex/php-imap/blob/5.2.0/src/Attachment.php#L252).\nEven if a developer passes a `$filename` into the `Attachment::save()` method, e.g. by passing the name or filename of the mail attachment itself (from email headers), the input values never get sanitized by the package.\nThere is also no restriction about the file extension (e.g. \".php\") or the contents of a file","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.3.0"]}],"null_published_at":"2026-10-31T22:13:10.058Z","source_updated_at":"2026-09-10T03:50:01.941Z","source_disclosed_at":"2023-06-21T21:58:58.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:49.666Z"}],"next_cursor":null,"snapshot_revision":"42594"}