dbcve.org
MailApplication · Nextcloud

CVE-2024-52508

HIGH · 8.1 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 1.14.6 / 1.15.4 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges 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 Mail is the mail app for Nextcloud, a self-hosted productivity platform. When a user is trying to set up a mail account with an email address like [email protected] that does not support auto configuration, and an attacker managed to register autoconfig.tld, the used email details would be send to the server of the attacker. It is recommended that the Nextcloud Mail app is upgraded to 1.14.6, 1.15.4, 2.2.11, 3.6.3, 3.7.7 or 4.0.0.

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-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure 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
MailApplication
Affected:>= 1.9.0, < 1.14.6>= 1.15.0, < 1.15.4>= 2.1.0, < 2.2.11>= 3.1.0, < 3.6.3>= 3.7.0, < 3.7.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 1.14.6 / 1.15.4 / 2.2.11 or later
Fixed in 1.14.61.15.42.2.11
Vendor patch github.com →
Recommended fix High confidence

Upgrade to 4.0.0 for the latest fixes, or to the latest stable version within your current major release branch (e.g., 3.6.3 if on 3.x, 2.2.11 if on 2.x, 1.15.4 if on 1.15.x, 1.14.6 if on 1.x)

  1. 1. Backup your Nextcloud instance and database before upgrading.
  2. 2. Access your Nextcloud server via SSH or terminal.
  3. 3. Navigate to your Nextcloud installation directory (e.g., /var/www/nextcloud).
  4. 4. Run the Nextcloud app upgrade command: occ app:update mail
  5. 5. Alternatively, update via the Nextcloud admin web interface: Go to Apps > Email > Enable update, or download the new version from the Nextcloud App Store and replace the mail app directory.
  6. 6. Verify the upgrade by checking the Mail app version in the Nextcloud admin settings under Apps > Email. Ensure the version matches one of the fixed releases: 1.14.6, 1.15.4, 2.2.11, 3.6.3, 3.7.7, or 4.0.0.
  7. 7. Test that auto-configuration no longer sends credentials to attacker-controlled domains by attempting to set up a new mail account.
Caveat No major breaking changes expected; this is primarily a security patch within version branches

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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