{"items":[{"id":"NVI-00006794","kind":"vulnerability","title":"Ez Platform and Legacy are prone to an insecure interpretation of PHP/PHAR uploads","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pqjm-xcp8-wgmm"],"plain_summary":"OSV carries this publisher advisory for ezsystems/ezpublish-legacy, ezsystems/ezpublish-legacy, ezsystems/ezpublish-legacy, ezsystems/ezpublish-legacy, ezsystems/ezpublish-legacy. 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 2018.9.1.3 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"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 2018.6.1.4 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"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 2017.12.4.3 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"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.4.12.3 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"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.12.6 for ezsystems/ezpublish-legacy. Confirm the publisher’s latest guidance.","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"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-c2c8275d71484751eb72a4031dccc5fe","url":"https://github.com/advisories/GHSA-pqjm-xcp8-wgmm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pqjm-xcp8-wgmm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.994Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"technology":"ezsystems/ezpublish-legacy","known_exclusions":[],"conditions_summary":"The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper.\n\n**1. WEB SERVER CONFIGURATION**\nThe sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/\n\nAs an example, here is how you can make Apache return HTTP 403 Forbidden for a number of executable file types in your eZ Platform var directory. Please adapt it to your needs. It is then possible to enable logging of HTTP 403 in a separate log file if you wish, you could do this to see if someone is trying to abuse the server.\n```\nRewriteEngine On\n\n# disable .php(3) and other extensions in the var directory\nRewriteRule ^var/.*(?i)\\.(php3?|phar|phtml|sh|exe|pl|bin)$ - [F]\n```\nHere is the same configuration, but for the Nginx web server:\n```\nlocation ~ ^/var/.*(?i)\\.(php3?|phar|p","public_affected_ranges":["ECOSYSTEM: introduced 2018.9.0; fixed 2018.9.1.3"]},{"certainty":"source_listed","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"technology":"ezsystems/ezpublish-legacy","known_exclusions":[],"conditions_summary":"The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper.\n\n**1. WEB SERVER CONFIGURATION**\nThe sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/\n\nAs an example, here is how you can make Apache return HTTP 403 Forbidden for a number of executable file types in your eZ Platform var directory. Please adapt it to your needs. It is then possible to enable logging of HTTP 403 in a separate log file if you wish, you could do this to see if someone is trying to abuse the server.\n```\nRewriteEngine On\n\n# disable .php(3) and other extensions in the var directory\nRewriteRule ^var/.*(?i)\\.(php3?|phar|phtml|sh|exe|pl|bin)$ - [F]\n```\nHere is the same configuration, but for the Nginx web server:\n```\nlocation ~ ^/var/.*(?i)\\.(php3?|phar|p","public_affected_ranges":["ECOSYSTEM: introduced 2018.6.0; fixed 2018.6.1.4"]},{"certainty":"source_listed","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"technology":"ezsystems/ezpublish-legacy","known_exclusions":[],"conditions_summary":"The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper.\n\n**1. WEB SERVER CONFIGURATION**\nThe sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/\n\nAs an example, here is how you can make Apache return HTTP 403 Forbidden for a number of executable file types in your eZ Platform var directory. Please adapt it to your needs. It is then possible to enable logging of HTTP 403 in a separate log file if you wish, you could do this to see if someone is trying to abuse the server.\n```\nRewriteEngine On\n\n# disable .php(3) and other extensions in the var directory\nRewriteRule ^var/.*(?i)\\.(php3?|phar|phtml|sh|exe|pl|bin)$ - [F]\n```\nHere is the same configuration, but for the Nginx web server:\n```\nlocation ~ ^/var/.*(?i)\\.(php3?|phar|p","public_affected_ranges":["ECOSYSTEM: introduced 2011.0.0; fixed 2017.12.4.3"]},{"certainty":"source_listed","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"technology":"ezsystems/ezpublish-legacy","known_exclusions":[],"conditions_summary":"The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper.\n\n**1. WEB SERVER CONFIGURATION**\nThe sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/\n\nAs an example, here is how you can make Apache return HTTP 403 Forbidden for a number of executable file types in your eZ Platform var directory. Please adapt it to your needs. It is then possible to enable logging of HTTP 403 in a separate log file if you wish, you could do this to see if someone is trying to abuse the server.\n```\nRewriteEngine On\n\n# disable .php(3) and other extensions in the var directory\nRewriteRule ^var/.*(?i)\\.(php3?|phar|phtml|sh|exe|pl|bin)$ - [F]\n```\nHere is the same configuration, but for the Nginx web server:\n```\nlocation ~ ^/var/.*(?i)\\.(php3?|phar|p","public_affected_ranges":["ECOSYSTEM: introduced 5.4.0; fixed 5.4.12.3"]},{"certainty":"source_listed","source_ids":["sr-c2c8275d71484751eb72a4031dccc5fe"],"technology":"ezsystems/ezpublish-legacy","known_exclusions":[],"conditions_summary":"The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper.\n\n**1. WEB SERVER CONFIGURATION**\nThe sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/\n\nAs an example, here is how you can make Apache return HTTP 403 Forbidden for a number of executable file types in your eZ Platform var directory. Please adapt it to your needs. It is then possible to enable logging of HTTP 403 in a separate log file if you wish, you could do this to see if someone is trying to abuse the server.\n```\nRewriteEngine On\n\n# disable .php(3) and other extensions in the var directory\nRewriteRule ^var/.*(?i)\\.(php3?|phar|phtml|sh|exe|pl|bin)$ - [F]\n```\nHere is the same configuration, but for the Nginx web server:\n```\nlocation ~ ^/var/.*(?i)\\.(php3?|phar|p","public_affected_ranges":["ECOSYSTEM: introduced 5.3.0; fixed 5.3.12.6"]}],"null_published_at":"2026-10-31T22:13:10.085Z","source_updated_at":"2024-11-29T05:44:57.691Z","source_disclosed_at":"2024-05-15T21:31:07.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:30.994Z"}],"next_cursor":null,"snapshot_revision":"42594"}