dbcve.org
Nextcloud Files Automated TaggingApplication · Nextcloud

CVE-2023-30539

HIGH · 8.8 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to 1.14.2 / 1.15.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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 is a personal home server system. Depending on the set up tags and other workflows this issue can be used to limit access of others or being able to grant them access when there are system tag based files access control or files retention rules. It is recommended that the Nextcloud Server is upgraded to 24.0.11 or 25.0.5, the Nextcloud Enterprise Server to 21.0.9.11, 22.2.10.11, 23.0.12.6, 24.0.11 or 25.0.5, and the Nextcloud Files automated tagging app to 1.11.1, 1.12.1, 1.13.1, 1.14.2, 1.15.3 or 1.16.1. Users unable to upgrade should disable all workflow related apps. Users are advised to upgrade.

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 Files Automated TaggingApplication
Affected:>= 1.14.0, < 1.14.2>= 1.15.0, < 1.15.3= 1.11.0= 1.12.0= 1.13.0= 1.16.0
Nextcloud ServerApplication
Affected:>= 21.0.0, < 21.0.9.11>= 22.0.0, < 22.2.10.11>= 23.0.0, < 23.0.12.6>= 24.0.0, < 24.0.11>= 25.0.0, < 25.0.5

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 1.14.2 / 1.15.3 / 21.0.9.11 or later
Fixed in 1.14.21.15.321.0.9.11
Vendor patch github.com →
Recommended fix High confidence

Nextcloud Server 24.0.11 or 25.0.5; Files Automated Tagging app 1.16.1

  1. 1. Back up your Nextcloud data and configuration before starting the upgrade
  2. 2. For Nextcloud Server: Upgrade to version 24.0.11 or 25.0.5 (recommended). For Enterprise Server, alternative fixed versions include 21.0.9.11, 22.2.10.11, or 23.0.12.6
  3. 3. For Nextcloud Files Automated Tagging app: Upgrade to version 1.16.1 (or minimum 1.14.2, 1.15.3, 1.13.1, 1.12.1, 1.11.1 depending on your release line)
  4. 4. After upgrade, verify that workflow-related apps (automated tagging, workflow engine, file retention) are functioning correctly
  5. 5. Test access control rules to confirm the improper access control vulnerability is remediated
  6. 6. If upgrade is not possible immediately, disable all workflow-related apps (Files Automated Tagging, Workflow Engine, File Retention) as a temporary mitigation
Caveat Review Nextcloud changelog for breaking changes between your current version and target version; major version jumps (e.g., 23 to 25) may have significant changes requiring testing

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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