dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2025-47791

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-16
Fix available
A fix is available. Upgrade to 28.0.13 / 29.0.10 or later.
See remediation →
62/100
Remediation priority · Elevated
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. In Nextcloud Server prior to 28.0.13, 29.0.10, and 30.0.3 and Nextcloud Enterprise Server prior to 28.0.13, 29.0.10, and 30.0.3, a currently unused endpoint to verify a share recipient was not protected correctly, allowing to proxy requests to another server. The endpoint was removed in Nextcloud Server 28.0.13, 29.0.10, and 30.0.3 and Nextcloud Enterprise Server 28.0.13, 29.0.10, and 30.0.3. No known workarounds are available.

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

The server can be induced to make requests to a URL an attacker controls, turning it into a proxy into internal networks and cloud metadata services. It's especially dangerous behind a trusted network boundary. The fix is strict allow-listing of destinations and blocking access to internal address ranges.

General guidance for the server-side request forgery (ssrf) 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:>= 28.0.0, < 28.0.13>= 29.0.0, < 29.0.10>= 30.0.0, < 30.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 28.0.13 / 29.0.10 / 30.0.3 or later
Fixed in 28.0.1329.0.1030.0.3
Vendor patch github.com →
Recommended fix High confidence

Nextcloud Server 28.0.13, 29.0.10, or 30.0.3 (whichever corresponds to the current major version line; recommend upgrading to latest stable 30.0.3 for longest support)

  1. 1. Create a complete backup of the Nextcloud database, data directory, and configuration files
  2. 2. Determine the current installed version (check occ config:system:get version or look at version.php in config/ directory)
  3. 3. Based on the current major version (28.x, 29.x, or 30.x), plan upgrade to the corresponding fixed release
  4. 4. Disable all third-party apps before upgrading to minimize compatibility issues
  5. 5. Run the standard Nextcloud upgrade process: occ maintenance:mode --on, then replace/update the Nextcloud files, then run occ upgrade
  6. 6. After upgrade completes, run occ maintenance:mode --off
  7. 7. Verify the upgrade was successful by logging in and checking the version in Administration > General settings
Caveat Standard Nextcloud upgrade risks apply: ensure backups before proceeding, verify third-party app compatibility with target version, and test in staging environment first if possible

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 $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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