dbcve.org
RichdocumentsApplication · Nextcloud

CVE-2023-25150

MEDIUM · 5.7 CVSS v3.1 Published 2023-02-08
Fix available
A fix is available. Upgrade to 3.8.7 / 4.2.9 or later.
See remediation →
61/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 office/richdocuments is an office suit for the nextcloud server platform. In affected versions the Collabora integration can be tricked to provide access to any file without proper permission validation. As a result any user with access to Collabora can obtain the content of other users files. It is recommended that the Nextcloud Office App (Collabora Integration) is updated to 7.0.2 (Nextcloud 25), 6.3.2 (Nextcloud 24), 5.0.10 (Nextcloud 23), 4.2.9 (Nextcloud 21-22), or 3.8.7 (Nextcloud 15-20). There are no known workarounds for this issue.

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
RichdocumentsApplication
Affected:< 3.8.7>= 4.0.0, < 4.2.9>= 5.0.0, < 5.0.10>= 6.0.0, < 6.3.2>= 7.0.0, < 7.0.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 3.8.7 / 4.2.9 / 5.0.10 or later
Fixed in 3.8.74.2.95.0.10
Vendor patch github.com →
Recommended fix High confidence

Richdocuments 3.8.7 (Nextcloud 15-20), 4.2.9 (Nextcloud 21-22), 5.0.10 (Nextcloud 23), 6.3.2 (Nextcloud 24), or 7.0.2 (Nextcloud 25)

  1. Identify the current Nextcloud version running in your environment
  2. Determine the corresponding Richdocuments version installed
  3. Upgrade to the appropriate fixed Richdocuments version based on your Nextcloud version: 3.8.7 (Nextcloud 15-20), 4.2.9 (Nextcloud 21-22), 5.0.10 (Nextcloud 23), 6.3.2 (Nextcloud 24), or 7.0.2 (Nextcloud 25)
  4. Use the Nextcloud app store or command line to update the Richdocuments app to the fixed version
  5. Verify the update was successful by checking the Richdocuments app version in the Nextcloud admin interface
  6. Test that file access controls are working properly with Nextcloud Office
Caveat Ensure the Richdocuments version is compatible with your Nextcloud version before upgrading; minor version updates typically have minimal breaking changes

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