dbcve.org
Nextcloud ServerApplication · Nextcloud

CVE-2023-39952

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-10
Fix available
A fix is available. Upgrade to 22.2.10.13 / 23.0.12.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 provides data storage for Nextcloud, an open source cloud platform. Starting in version 22.0.0 and prior to versions 22.2.10.13, 23.0.12.8, 24.0.12.4, 25.0.8, 26.0.3, and 27.0.1, a user can access files inside a subfolder of a groupfolder accessible to them, even if advanced permissions would block access to the subfolder. Nextcloud Server versions 25.0.8, 26.0.3, and 27.0.1 and Nextcloud Enterprise Server versions 22.2.10.13, 23.0.12.8, 24.0.12.4, 25.0.8, 26.0.3, and 27.0.1 contain a patch for this issue. 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-284

The application fails to correctly restrict what a user can do or reach, so functions or resources are available to people who should not have them. Attackers simply probe for the paths where the check is missing or wrong. The fix is to enforce access-control decisions consistently on every request, evaluated against the acting user rather than assumed from context.

General guidance for the improper access control 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:>= 22.0.0, < 22.2.10.13>= 23.0.0, < 23.0.12.8>= 24.0.0, < 24.0.12.4>= 25.0.0, < 25.0.8>= 26.0.0, < 26.0.3= 27.0.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 22.2.10.13 / 23.0.12.8 / 24.0.12.4 or later
Fixed in 22.2.10.1323.0.12.824.0.12.4
Vendor patch github.com →
Recommended fix High confidence

Upgrade to Nextcloud Server 22.2.10.13, 23.0.12.8, 24.0.12.4, or 25.0.8 (or higher) depending on your current major version line

  1. 1. Identify the currently installed Nextcloud Server version using the web interface (Settings > Administration > Overview) or occ command: `occ --version`
  2. 2. Determine the appropriate target version based on your current major version (22.x → 22.2.10.13, 23.x → 23.0.12.8, 24.x → 24.0.12.4, or 25.x → 25.0.8)
  3. 3. Review the Nextcloud upgrade documentation for your version at https://docs.nextcloud.com/server/stable/admin_manual/maintenance/upgrade.html
  4. 4. Create a full backup of the Nextcloud instance including database and data directory
  5. 5. Ensure PHP and database requirements are met for the target version
  6. 6. Run the upgrade using theocc command: `occ upgrade`
  7. 7. Verify the upgrade completed successfully and check the admin overview page for any warnings
  8. 8. Confirm the security patch is applied by checking the version number matches the fixed release
Caveat Major version upgrades (e.g., 25 to 26) may require additional migration steps and compatibility checks for apps and custom configurations

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-2023-39952 — 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-2023-39952 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