{"items":[{"id":"NVI-00004699","kind":"vulnerability","title":"Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling","revision":5,"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-wc7j-g8wx-m2qx","CVE-2026-45260"],"plain_summary":"GitHub lists this reviewed advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1d334a0c72df636c6d02c4f1e45c346d"],"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},{"summary":"The original advisory lists fixed boundaries 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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":[{"kind":"CVSS","as_of":"2026-07-10T19:08:23.000Z","value":"8.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-55acbf2fe326ff8d3cfd437eb51cbae6"},{"kind":"CVSS","as_of":"2026-07-23T16:04:11.740Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-632b6bebf86f86b5306b9d34744380d5"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.636%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.50545. Missing scores are unknown.","source_id":"sr-1d334a0c72df636c6d02c4f1e45c346d"}],"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-55acbf2fe326ff8d3cfd437eb51cbae6","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:34:12.429Z"},{"id":"sr-6fd4efd9a0d721df833ffa83e2df918a","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-632b6bebf86f86b5306b9d34744380d5","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45260","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-45260","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-1d334a0c72df636c6d02c4f1e45c346d","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-2026-45260","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.785Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-55acbf2fe326ff8d3cfd437eb51cbae6"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":[">= 12.0.0-RC1, <= 12.3.6"]},{"certainty":"source_listed","source_ids":["sr-55acbf2fe326ff8d3cfd437eb51cbae6"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":[">= 2026.1.0, < 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-55acbf2fe326ff8d3cfd437eb51cbae6"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["<= 11.5.16"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]}],"null_published_at":"2026-11-07T14:01:55.405Z","source_updated_at":"2026-07-10T19:08:23.000Z","source_disclosed_at":"2026-05-27T17:17:18.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-00004699","kind":"vulnerability","title":"Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling","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-wc7j-g8wx-m2qx","CVE-2026-45260"],"plain_summary":"GitHub lists this reviewed advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-17e4b62aee0c3b0888f5a6a478a2811e"],"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},{"summary":"The original advisory lists fixed boundaries 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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":[{"kind":"CVSS","as_of":"2026-07-10T19:08:23.000Z","value":"8.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-55acbf2fe326ff8d3cfd437eb51cbae6"},{"kind":"CVSS","as_of":"2026-07-23T16:04:11.740Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-632b6bebf86f86b5306b9d34744380d5"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.636%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.50505. Missing scores are unknown.","source_id":"sr-17e4b62aee0c3b0888f5a6a478a2811e"}],"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-55acbf2fe326ff8d3cfd437eb51cbae6","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:34:12.429Z"},{"id":"sr-6fd4efd9a0d721df833ffa83e2df918a","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-632b6bebf86f86b5306b9d34744380d5","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45260","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-45260","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-17e4b62aee0c3b0888f5a6a478a2811e","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-2026-45260","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-55acbf2fe326ff8d3cfd437eb51cbae6"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":[">= 12.0.0-RC1, <= 12.3.6"]},{"certainty":"source_listed","source_ids":["sr-55acbf2fe326ff8d3cfd437eb51cbae6"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":[">= 2026.1.0, < 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-55acbf2fe326ff8d3cfd437eb51cbae6"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["<= 11.5.16"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]}],"null_published_at":"2026-11-05T19:10:21.460Z","source_updated_at":"2026-07-10T19:08:23.000Z","source_disclosed_at":"2026-05-27T17:17:18.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-00004699","kind":"vulnerability","title":"Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling","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-wc7j-g8wx-m2qx","CVE-2026-45260"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. 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 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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-17e4b62aee0c3b0888f5a6a478a2811e"],"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-07-23T16:04:11.740Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-632b6bebf86f86b5306b9d34744380d5"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.636%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.50505. Missing scores are unknown.","source_id":"sr-17e4b62aee0c3b0888f5a6a478a2811e"}],"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-6fd4efd9a0d721df833ffa83e2df918a","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-632b6bebf86f86b5306b9d34744380d5","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45260","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-45260","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-17e4b62aee0c3b0888f5a6a478a2811e","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-2026-45260","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]}],"null_published_at":"2026-11-02T20:21:10.297Z","source_updated_at":"2026-07-10T19:15:11.884Z","source_disclosed_at":"2026-05-27T17:17:18.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-00004699","kind":"vulnerability","title":"Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-wc7j-g8wx-m2qx","CVE-2026-45260"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. 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 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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-17e4b62aee0c3b0888f5a6a478a2811e"],"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.636%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.50505. Missing scores are unknown.","source_id":"sr-17e4b62aee0c3b0888f5a6a478a2811e"}],"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-6fd4efd9a0d721df833ffa83e2df918a","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-17e4b62aee0c3b0888f5a6a478a2811e","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-2026-45260","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]}],"null_published_at":"2026-10-31T22:27:06.727Z","source_updated_at":"2026-07-10T19:15:11.884Z","source_disclosed_at":"2026-05-27T17:17:18.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-00004699","kind":"vulnerability","title":"Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-wc7j-g8wx-m2qx","CVE-2026-45260"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. 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 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"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-6fd4efd9a0d721df833ffa83e2df918a","url":"https://github.com/advisories/GHSA-wc7j-g8wx-m2qx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wc7j-g8wx-m2qx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]},{"certainty":"source_listed","source_ids":["sr-6fd4efd9a0d721df833ffa83e2df918a"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\nPimcore's WebDAV asset endpoint exposes a `MOVE` operation through `/asset/webdav{path}` without adding an authentication plugin in the WebDAV controller. The `Tree::move()` implementation then performs asset mutation and deletion before checking a current Pimcore user or any asset permissions.\n\nAn unauthenticated remote attacker who knows two existing asset paths in the same directory can send a WebDAV `MOVE` request that deletes the source asset. Authenticated low-privileged users may also be able to perform unauthorized asset move or overwrite operations because the move path does not enforce `rename`, `delete`, `create`, or `publish` permissions.\n\n### Details\nThe route for WebDAV is globally registered and accepts arbitrary trailing paths:\n\n```yaml\n# bundles/CoreBundle/config/routing.yaml\npimcore_webdav:\n    path: /asset/webdav{path}\n    defaults: { _controller: Pimcore\\Bundle\\CoreBundle\\Controller\\WebDavController::webdavAction }\n    requirements:\n        path: '.*'\n```\n\nThe controller constructs a SabreDAV server but only attaches lock and browser plugins. It does not attach an authentication plugin or perform an explicit user/session check before starting the ser","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]}],"null_published_at":"2026-10-31T22:12:57.139Z","source_updated_at":"2026-07-10T19:15:11.884Z","source_disclosed_at":"2026-05-27T17:17:18.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"}