dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2023-32319

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-26
Fix available
A fix is available. Upgrade to 24.0.11 / 25.0.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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
Nextcloud server is an open source personal cloud implementation. Missing brute-force protection on the WebDAV endpoints via the basic auth header allowed to brute-force user credentials when the provided user name was not an email address. Users from version 24.0.0 onward are affected. This issue has been addressed in releases 24.0.11, 25.0.5 and 26.0.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nextcloud ServerApplication
Affected:>= 24.0.0, < 24.0.11>= 25.0.0, < 25.0.5

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
None
Availability
None

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

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
Upgrade available Upgrade to 24.0.11 / 25.0.5 or later
Fixed in 24.0.1125.0.5
Vendor patch github.com →
Recommended fix High confidence

24.0.11, 25.0.5, or 26.0.0 (latest stable)

  1. 1. Backup your Nextcloud data and database before upgrading.
  2. 2. Identify your current Nextcloud version in the web UI (Settings > Administration > Overview) or via occ commands.
  3. 3. If running 24.0.0-24.0.10, upgrade to 24.0.11 or later (preferably 26.0.0 or latest stable).
  4. 4. If running 25.0.0-25.0.4, upgrade to 25.0.5 or later (preferably 26.0.0 or latest stable).
  5. 5. Use the official Nextcloud upgrade method (web installer, archive, or package manager) to perform the upgrade.
  6. 6. Verify the upgrade was successful by logging in and checking the version in Administration > Overview.
  7. 7. Test WebDAV functionality to ensure the brute-force protection is working correctly.
Caveat Major version upgrades in Nextcloud may introduce breaking changes; review the changelog for your upgrade path before proceeding

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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