VulnerabilityPublished 16 Oct 2025

CVE-2025-58051: nextcloud security-advisories · Improper Enforcement of Behavioral Workflow

Affects nextcloud security-advisoriesSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 0.9.5 : update nextcloud security-advisories when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.9.5, 0.8.8, 0.7.6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nextcloud/tables to 0.9.5, 0.8.8 or 0.7.6.

Affected software

Product	Affected	Fixed in
GitHubnextcloud/tables`pkg:github/nextcloud/tables`Other threats	Affected <0.7.6 >=0.7.6 <0.8.8 >=0.8.8 <0.9.5	Fixed in 0.7.6 0.8.8 0.9.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Nextcloud Tables to versions 0.7.6, 0.8.8, or 0.9.5 or later immediately to apply the fix for this vulnerability.
Restrict user permissions to minimize the number of users who can import tables, especially limiting access to trusted users only.
Implement strict monitoring and logging of import activities within Nextcloud to detect any unusual file import attempts referencing server files.
Conduct regular audits of file permissions and server file accessibility to reduce the risk of sensitive files being accessible through the import process.
Employ network segmentation and access controls to limit exposure of Nextcloud servers to only trusted networks and users.
Educate users about the risks of importing data from untrusted sources and enforce strong authentication mechanisms to prevent account compromise.
Consider additional application-layer controls or custom filters to validate imported file paths if upgrading is delayed.

Description

Nextcloud Tables allows you to create your own tables with individual columns. Prior 0.7.6, 0.8.8, and 0.9.5, when importing a table, a user was able to specify files on the server and when their format is supported by the used PhpSpreadsheet library they would be included and their content leaked to the user. It is recommended that the Nextcloud Tables app is upgraded to 0.7.6, 0.8.8 or 0.9.5.

Impact

For European organizations, this vulnerability poses a risk of unauthorized disclosure of sensitive server-side files through the Nextcloud Tables import feature. Since Nextcloud is widely used in Europe for collaboration and file sharing, especially in public sector, education, and enterprises, the exposure of confidential data could lead to privacy violations, regulatory non-compliance (e.g., GDPR), and reputational damage. The vulnerability requires authenticated access, so insider threats or compromised user accounts could exploit it to leak sensitive information. Although it does not affect system integrity or availability, the confidentiality breach could expose intellectual property, personal data, or configuration files, potentially facilitating further attacks. Organizations relying on Nextcloud Tables for data management should consider this a significant data leakage risk and prioritize remediation to maintain compliance and trust.

CWE-841Improper Enforcement of Behavioral Workflow (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.1 (opens in a new tab)
V11.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 17:14 UTC

WeaknessesCWE-841

Technical details

References

Community reviews

Related threats