dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2025-59788

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 22.2.10.33 / 23.0.12.29 or later.
See remediation →
58/100
Remediation priority · Elevated
Public exploit Remotely reachable

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
Cross-site scripting (XSS) vulnerability in a reachable files_pdfviewer example directory in Nextcloud with versions before 22.2.10.33, 23.0.12.29, 24.0.12.28, 25.0.13.23, 26.0.13.20, 27.1.11.20, 28.0.14.11, 29.0.16.8, 30.0.17, 31.0.10, and 32.0.1 allows attackers to execute arbitrary JavaScript in the context of a user's browser via a crafted PDF file to viewer.html. This issue is related to CVE-2024-4367, but the root cause of this Nextcloud issue is that the product exposes executable example code on a same-origin basis.

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:>= 30.0.0, < 30.0.17>= 31.0.0, < 31.0.10>= 32.0.0, < 32.0.1>= 22.0.0, < 22.2.10.33>= 23.0.0, < 23.0.12.29>= 24.0.0, < 24.0.12.28>= 25.0.0, < 25.0.13.23>= 26.0.0, < 26.0.13.20>= 27.0.0, < 27.1.11.20>= 28.0.0, < 28.0.14.11>= 29.0.0, < 29.0.16.8

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 22.2.10.33 / 23.0.12.29 / 24.0.12.28 or later
Fixed in 22.2.10.3323.0.12.2924.0.12.28
Recommended fix High confidence

Nextcloud Server 30.0.17, 31.0.10, 32.0.1, or 22.2.10.33 (depending on your major version branch)

  1. 1. Identify the currently installed Nextcloud Server version using the web interface (Settings > Administration > Overview) or occ command: 'occ --version'
  2. 2. Based on your current major version line, upgrade to the corresponding fixed release: For Nextcloud 30.x: upgrade to 30.0.17; For Nextcloud 31.x: upgrade to 31.0.10; For Nextcloud 32.x: upgrade to 32.0.1; For Nextcloud 22.x: upgrade to 22.2.10.33
  3. 3. Before upgrading, perform a full backup of the Nextcloud data directory, database, and configuration files
  4. 4. Review the Nextcloud upgrade documentation for your deployment method (package manager, Docker, or manual)
  5. 5. Execute the upgrade following standard Nextcloud upgrade procedures, ensuring maintenance mode is enabled during the process
  6. 6. After upgrade, clear browser cache and verify the version number reflects the fixed release
  7. 7. Test the files_pdfviewer functionality to confirm the example directory is no longer accessible or has been patched
Caveat Standard Nextcloud upgrade risks apply: review changelog for deprecations, ensure app compatibility, and test in staging first. Downgrading is not supported.

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