dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2025-47790

MEDIUM · 6.4 CVSS v3.1 Published 2025-05-16
Fix available
A fix is available. Upgrade to 26.0.13.15 / 27.1.11.15 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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. Nextcloud Server prior to 29.0.15, 30.0.9, and 31.0.3 and Nextcloud Enterprise Server prior to 26.0.13.15, 27.1.11.15, 28.0.14.6, 29.0.15, 30.0.9, and 31.0.3 have a bug with session handling. The bug caused skipping the second factor confirmation after a successful login with the username and password when the server was configured with `remember_login_cookie_lifetime` set to `0`, once the session expired on the page to select the second factor and the page is reloaded. Nextcloud Server 29.0.15, 30.0.9, and 31.0.3 and Nextcloud Enterprise Server is upgraded to 26.0.13.15, 27.1.11.15, 28.0.14.6, 29.0.15, 30.0.9 and 31.0.3 contain a patch. As a workaround, set the `remember_login_cookie_lifetime` in config.php to a value other than `0`, e.g. `900`. Beware that this is only a workaround for new sessions created after the configuration change. System administration can delete affected sessions.

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:>= 26.0.0, < 26.0.13.15>= 27.0.0, < 27.1.11.15>= 28.0.0, < 28.0.14.6>= 29.0.0, < 29.0.15>= 30.0.0, < 30.0.9>= 31.0.0, < 31.0.3

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

CVSS:3.1/AV:N/AC:H/PR:L/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 26.0.13.15 / 27.1.11.15 / 28.0.14.6 or later
Fixed in 26.0.13.1527.1.11.1528.0.14.6
Vendor patch github.com →
Recommended fix High confidence

Upgrade to 26.0.13.15 (for 26.x), 27.1.11.15 (for 27.x), 28.0.14.6 (for 28.x), 29.0.15 (for 29.x), 30.0.9 (for 30.x), or 31.0.3 (for 31.x) depending on your current major version

  1. 1. Back up your Nextcloud database and data directory before proceeding with any upgrade.
  2. 2. Review your current Nextcloud version by checking the version number in the admin settings.
  3. 3. For Nextcloud 26.x: Upgrade to version 26.0.13.15 or later.
  4. 4. For Nextcloud 27.x: Upgrade to version 27.1.11.15 or later.
  5. 5. For Nextcloud 28.x: Upgrade to version 28.0.14.6 or later.
  6. 6. For Nextcloud 29.x: Upgrade to version 29.0.15 or later.
  7. 7. For Nextcloud 30.x: Upgrade to version 30.0.9 or later.
  8. 8. For Nextcloud 31.x: Upgrade to version 31.0.3 or later.
Caveat Standard Nextcloud upgrade considerations apply - review the changelog for your target version for any breaking changes between your current and 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,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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