dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-45260

HIGH · 8.1 CVSS v3.1 Published 2026-07-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.7, Pimcore's WebDAV asset endpoint exposes a MOVE operation through /asset/webdav{path} without an authentication plugin in bundles/CoreBundle/src/Controller/WebDavController.php, and models/Asset/WebDAV/Tree.php performs asset mutation and deletion through models/Asset.php before checking a current Pimcore user or the rename, delete, create, or publish permissions, allowing unauthorized asset deletion, moves, or overwrites. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WebDAV endpoint in Pimcore (/asset/webdav{path}) exposes a MOVE operation without an authentication plugin. Code in WebDavController.php and Tree.php performs asset mutations and deletions through Asset.php BEFORE checking for a current Pimcore user or checking rename, delete, create, or publish permissions, allowing unauthenticated or unauthorized attackers to delete, move, or overwrite any asset.

MitigationUpgrade to Pimcore 11.5.17 (LTS) or 12.3.7 or later which adds proper authentication and authorization checks before WebDAV asset operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pimcore installation and version
    Check your composer.json or the system settings in the Pimcore admin panel to determine the installed Pimcore version. Compare against 11.5.17 (LTS) and 12.3.7 fixed versions.
    Affected if The installed version is below 11.5.17 or 12.3.7 (or is an intermediate version between 11.x and 12.x families that falls before 12.3.7).
  2. Verify WebDAV endpoint accessibility
    Inspect your web server configuration (Apache/Nginx) and Pimcore routing to confirm the /asset/webdav endpoint is accessible. Attempt an unauthenticated HTTP request to /asset/webdav/ (note: do not actually perform mutations, just verify the endpoint responds).
    Affected if The WebDAV endpoint responds without requiring authentication credentials.
  3. Inspect WebDavController.php for missing authorization
    Locate the file vendor/pimcore/pimcore/bundles/AdminBundle/Controller/WebDAV/WebDavController.php (or similar path in your installation). Search for move(), delete(), or put() methods that call Asset operations without preceding $this->checkPermission() or $this->getUser() calls.
    Affected if Asset mutation methods (move, delete, put) lack authentication checks or permission verifications before executing Asset.php operations.
  4. Inspect Tree.php for missing permission checks
    Locate the file vendor/pimcore/pimcore/models/Asset/WebDAV/Tree.php (or similar path). Examine delete() and move() methods to verify whether they invoke permission checks (rename, delete, create, publish) before performing asset operations.
    Affected if The Tree.php delete and move methods perform asset operations without first calling permission validation functions.

Your environment is affected if you run a Pimcore version below 11.5.17 or 12.3.7 AND the WebDAV endpoint at /asset/webdav is accessible without requiring authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Pimcore 11.5.17 (LTS) or 12.3.7 or later which adds proper authentication and authorization checks before WebDAV asset operations.

Recommended fix High confidence

11.5.17 (LTS) or 12.3.7 depending on your current branch

  1. Backup your Pimcore database and all files before upgrading
  2. Identify your current Pimcore version by checking the installed composer packages or admin panel
  3. If running Pimcore 11.x (LTS branch): Upgrade to version 11.5.17
  4. If running Pimcore 12.x: Upgrade to version 12.3.7
  5. Run database migrations after upgrading (php bin/console pimcore:migrations:migrate or similar)
  6. Clear the application cache
  7. Verify that the WebDAV endpoint now properly checks authentication and permissions before allowing asset operations
  8. Test that authorized users can still perform WebDAV operations (move, delete, rename) as expected
Caveat Pimcore minor version upgrades may include breaking changes; review the changelog/release notes for your version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45260 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data