dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-54563

HIGH · 7.1 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 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
Cloudreve is a self-hosted file management and sharing system. Prior to 4.16.1, a Cloudreve WebDAV account rooted at a configured folder can send paths such as /dav/%2e%2e/outside.txt because stripPrefix in pkg/webdav/webdav.go joins the decoded request suffix to the account root with fs.URI.JoinRaw without checking containment, allowing the scoped credential to read and list files outside the configured folder and writable credentials to create, overwrite, move, or delete them. This issue is reported as fixed in version 4.16.1.

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

Cloudreve's WebDAV component suffers from a path traversal vulnerability in the stripPrefix function (pkg/webdav/webdav.go). The function joins the decoded request path suffix to the account root using fs.URI.JoinRaw without validating containment, allowing authenticated WebDAV users to escape the scoped folder using URL-encoded path traversal sequences like %2e%2e (../). Read-only credentials can list and read files outside the scope; writable credentials can also create, modify, move, or delete files outside the configured folder.

MitigationUpgrade to Cloudreve version 4.16.1 or later, which implements proper path containment validation in the WebDAV stripPrefix function to prevent directory traversal.

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
High
Integrity
Low
Availability
None

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

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. Check Cloudreve installation and version
    Locate the Cloudreve binary or Docker container, then run 'cloudreve --version' or inspect the container image tag to determine the installed version.
    Affected if The installed version is earlier than 4.16.1 (the first version with the fix).
  2. Confirm WebDAV is enabled
    Examine the Cloudreve configuration file (usually conf.ini or config.yaml) for the [webdav] section, or check if the /webdav endpoint responds to requests.
    Affected if WebDAV is enabled and accessible - the vulnerability only applies when the WebDAV component is running.
  3. Identify WebDAV user accounts
    Log into the Cloudreve admin panel and navigate to User Management, or query the database for users with WebDAV access permissions.
    Affected if There are one or more WebDAV users configured - exploitation requires authenticated access.
  4. Test for path traversal vulnerability
    Using a WebDAV client (such as cadaver or a tool like curl with PROPFIND/GET requests), attempt to access a path outside the user's configured storage scope by using URL-encoded traversal sequences (e.g., request /webdav/%2e%2e%2f..%2f).
    Affected if The response returns files or allows operations outside the user's assigned root folder, indicating the path containment check is missing.

A user is affected if they run a Cloudreve version below 4.16.1 with WebDAV enabled and have WebDAV-accessible user accounts, allowing authenticated users to escape their scoped folder via path traversal sequences.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cloudreve version 4.16.1 or later, which implements proper path containment validation in the WebDAV stripPrefix function to prevent directory traversal.

Recommended fix Moderate confidence

4.16.1

  1. 1. Back up your current Cloudreve installation and configuration
  2. 2. Download Cloudreve version 4.16.1 from the official GitHub releases page
  3. 3. Stop the Cloudreve service
  4. 4. Replace the existing Cloudreve binary with the new version 4.16.1
  5. 5. Review the release notes for any required configuration changes
  6. 6. Start the Cloudreve service
  7. 7. Verify that WebDAV functionality works correctly with scoped accounts
  8. 8. Test that path traversal is no longer possible (e.g., attempting /dav/%2e%2e/ outside.txt should be denied)
Caveat Review release notes for any breaking changes between your current version and 4.16.1

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing5.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,430
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54563 — 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-54563 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