dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2024-37313

HIGH · 7.5 CVSS v3.1 Published 2024-06-14
Fix available
A fix is available. Upgrade to 21.0.9.17 / 22.2.10.22 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 a self hosted personal cloud system. Under some circumstance it was possible to bypass the second factor of 2FA after successfully providing the user credentials. It is recommended that the Nextcloud Server is upgraded to 26.0.13, 27.1.8 or 28.0.4 and Nextcloud Enterprise Server is upgraded to 21.0.9.17, 22.2.10.22, 23.0.12.17, 24.0.12.13, 25.0.13.8, 26.0.13, 27.1.8 or 28.0.4.

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
How this class of weakness works · CWE-287

The mechanism that verifies who a user is can be side-stepped or fooled, letting an attacker act as someone they're not. Everything built on top of that identity then becomes untrustworthy. Fixing it means hardening the full authentication flow, including edge cases, tokens, and secondary paths.

General guidance for the improper authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 21.0.0, < 21.0.9.17>= 22.0.0, < 22.2.10.22>= 23.0.0, < 23.0.12.17>= 24.0.0, < 24.0.12.13>= 25.0.0, < 25.0.13.8>= 26.0.0, < 26.0.13>= 27.0.0, < 27.1.8>= 28.0.0, < 28.0.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 21.0.9.17 / 22.2.10.22 / 23.0.12.17 or later
Fixed in 21.0.9.1722.2.10.2223.0.12.17
Vendor patch github.com →
Recommended fix High confidence

21.0.9.17, 22.2.10.22, 23.0.12.17, or 24.0.12.13 (or 26.0.13/27.1.8/28.0.4 for newer major versions)

  1. 1. Identify the currently installed Nextcloud Server version using the web interface (Settings > Administration > Overview) or occ command: occ --version
  2. 2. Based on the current version, determine the appropriate upgrade path: if 21.0.0-21.0.9.16 upgrade to 21.0.9.17; if 22.0.0-22.2.10.21 upgrade to 22.2.10.22; if 23.0.0-23.0.12.16 upgrade to 23.0.12.17; if 24.0.0-24.0.12.12 upgrade to 24.0.12.13; or upgrade to 26.0.13, 27.1.8, or 28.0.4 for newer major versions
  3. 3. Before upgrading, backup the Nextcloud data directory, database, and config.php file
  4. 4. Place Nextcloud in maintenance mode: occ maintenance:mode --on
  5. 5. Download the target version from https://nextcloud.com/install/#install-clients or use the built-in updater
  6. 6. Extract the new version over the existing installation, preserving config.php and data directory
  7. 7. Run database migrations: occ db:migrate
  8. 8. Disable maintenance mode: occ maintenance:mode --off
Caveat Major version upgrades (e.g., 24 to 26+) may require PHP version updates and app compatibility checks; review Nextcloud changelog before upgrading

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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