LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32655: Files Drop public link can be added as federated share

Nextcloud Server is a Nextcloud package that handles data storage. In versions prior to 19.0.11, 20.0.10, and 21.0.2, an attacker is able to convert a Files Drop link to a federated share. This causes an issue on the UI side of the sharing user. When the sharing user opens the sharing panel and tries to remove the "Create" privileges of this unexpected share, Nextcloud server would silently grant the share read privileges. The vulnerability is patched in versions 19.0.11, 20.0.10 and 21.0.2. No workarounds are known to exist.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity Nextcloud Server sharing flaw. A user with access could turn a Files Drop public link into an unexpected federated share. A later UI action by the sharing user could accidentally grant read access. The business risk is unintended exposure of shared files, not system takeover.

Executive priority

Treat this as a scheduled patching item unless sensitive external sharing is common. It is not a crisis-level vulnerability, but it can create unwanted data exposure and should be closed in routine security maintenance.

Technical view

Affected Nextcloud Server versions before 19.0.11, 20.0.10, and 21.0.2 mishandle Files Drop links converted to federated shares. When the owner opens the sharing panel and removes Create privileges, the server silently grants read privileges. CVSS 3.5 reflects network access, low complexity, required privileges, required user interaction, and low confidentiality impact.

Likely exposure

Exposure is limited to organizations running affected Nextcloud Server versions with Files Drop/public-link sharing and federation features in use. The issue does not apply once patched to 19.0.11, 20.0.10, 21.0.2, or later.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires a privileged user and user interaction by the sharing user. The impact described is unintended read access through share-permission handling.

Researcher notes

Evidence supports a narrow confidentiality issue in Nextcloud share-permission handling. The source bundle names fixed versions and states no workarounds. It does not provide evidence of broad exploitation, weaponization, or impacts beyond unintended read privileges.

Mitigation direction

  • Upgrade Nextcloud Server to 19.0.11, 20.0.10, 21.0.2, or later.
  • Do not rely on workaround mitigation; the advisory states none are known.
  • Check Nextcloud vendor guidance for any deployment-specific instructions.
  • Review exposed Files Drop and federated sharing settings during upgrade planning.

Validation and detection

  • Inventory all Nextcloud Server instances and record exact versions.
  • Confirm every affected branch is patched to the fixed version or later.
  • Review public Files Drop links for unexpected federated shares.
  • Check available audit logs for unusual share creation or permission changes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-241: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32655 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.5CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2021-32655Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nextcloudsecurity-advisories< 19.0.11, >= 20.0.0, < 20.0.10, >= 21.0.0, < 21.0.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-241 · source CWE mapping

Improper Handling of Unexpected Data Type

Improper Handling of Unexpected Data Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.