dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2024-52519

HIGH · 8.2 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 27.1.11.8 / 28.0.10 or later.
See remediation →
91/100
Remediation priority · Urgent
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. The OAuth2 client secrets were stored in a recoverable way, so that an attacker that got access to a backup of the database and the Nextcloud config file, would be able to decrypt them. It is recommended that the Nextcloud Server is upgraded to 28.0.10 or 29.0.7 and Nextcloud Enterprise Server is upgraded to 27.1.11.8, 28.0.10 or 29.0.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

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:>= 27.0.0, < 27.1.11.8>= 28.0.0, < 28.0.10>= 29.0.0, < 29.0.7

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

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

27.1.11.8, 28.0.10, or 29.0.7 (depending on your current major version)

  1. 1. Create a complete backup of the Nextcloud database and config/config.php file before proceeding
  2. 2. Ensure you have a backup of all user data files
  3. 3. Download the appropriate fixed version: 27.1.11.8 (for 27.x), 28.0.10 (for 28.x), or 29.0.7 (for 29.x)
  4. 4. Place the server in maintenance mode: sudo -u www-data php occ maintenance:mode --on
  5. 5. Replace the Nextcloud installation files with the new version
  6. 6. Run the upgrade command: sudo -u www-data php occ upgrade
  7. 7. Clear any caching mechanisms used (Redis, Memcached)
  8. 8. Verify OAuth2 functionality is working correctly post-upgrade
Caveat Standard Nextcloud upgrade best practices apply - verify app compatibility and backup 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-52519 — 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-52519 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