dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2024-52525

HIGH · 7.5 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 28.0.12 / 29.0.9 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 certain conditions the password of a user was stored unencrypted in the session data. The session data is encrypted before being saved in the session storage (Redis or disk), but it would allow a malicious process that gains access to the memory of the PHP process, to get access to the cleartext password of the user. It is recommended that the Nextcloud Server is upgraded to 28.0.12, 29.0.9 or 30.0.2.

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:>= 28.0.0, < 28.0.12>= 29.0.0, < 29.0.9>= 30.0.0, < 30.0.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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 28.0.12 / 29.0.9 / 30.0.2 or later
Fixed in 28.0.1229.0.930.0.2
Vendor patch github.com →
Recommended fix High confidence

Nextcloud Server 28.0.12, 29.0.9, or 30.0.2 (choose based on your major version branch)

  1. Back up your Nextcloud data directory, database, and configuration files before upgrading
  2. Stop the web server (e.g., Apache, Nginx) to prevent new sessions during upgrade
  3. Update your Nextcloud installation using your package manager (e.g., `apt update && apt upgrade nextcloud` or equivalent for your distribution)
  4. Alternatively, download and install the specific version (28.0.12, 29.0.9, or 30.0.2) from the official Nextcloud downloads page and follow the manual upgrade procedure
  5. Restart the web server after the upgrade completes
  6. Clear the session cache (e.g., flush Redis if used for sessions, or delete session files)
  7. Log in and verify that users can authenticate successfully
  8. Review the Nextcloud admin settings to confirm the system is functioning correctly
Caveat Standard upgrade risks apply: test in staging first, review changelog for deprecations, and ensure apps/plugins are compatible with the target version

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-52525 — 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-52525 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