VulnerabilityPublished 18 Jan 2024Updated 9 Jun 2025

CVE-2024-22402: nextcloud security-advisories · Improper Preservation of Permissions

Affects nextcloud security-advisoriesSource CVE Database V5

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.1, 2.5.1, 2.4.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 18 Jan 2024
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/guests to 3.0.1, 2.5.1 or 2.4.1.

Affected software

Product	Affected	Fixed in
GitHubnextcloud/guests`pkg:github/nextcloud/guests`Other threats	Affected <2.4.1 >=2.4.1 <2.5.1 >=2.5.1 <3.0.1	Fixed in 2.4.1 2.5.1 3.0.1

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

AI-suggested

European organizations should prioritize upgrading the Nextcloud Guests app to the fixed versions 2.4.1, 2.5.1, or 3.0.1 without delay. Beyond patching, organizations should audit their Nextcloud configurations to ensure minimal app installations and restrict guest user permissions strictly. Implementing network segmentation and access controls can limit exposure of Nextcloud instances to trusted networks only. Monitoring and logging access to Nextcloud apps should be enhanced to detect unusual access patterns indicative of exploitation attempts. Additionally, organizations should review their guest user policies and consider temporary suspension of guest access until patches are applied. Regular vulnerability scanning and integration of Nextcloud security advisories into patch management workflows will help maintain ongoing security.

Description

Nextcloud guests app is a utility to create guest users which can only see files shared with them. In affected versions users were able to load the first page of apps they were actually not allowed to access. Depending on the selection of apps installed this may present a permissions bypass. It is recommended that the Guests app is upgraded to 2.4.1, 2.5.1 or 3.0.1. There are no known workarounds for this vulnerability.

Impact

For European organizations, the impact of CVE-2024-22402 can be significant, especially for those relying on Nextcloud for file sharing and collaboration. Unauthorized access to app pages could lead to exposure of sensitive corporate or personal data, violating data protection regulations such as GDPR. This could result in legal penalties, reputational damage, and loss of trust. The integrity of shared data could also be compromised if unauthorized users manipulate app functionalities. Since Nextcloud is popular among European public sector entities, educational institutions, and enterprises valuing data sovereignty, the vulnerability could affect a broad range of organizations. The lack of known exploits reduces immediate risk, but the ease of exploitation and network accessibility mean attackers could leverage this flaw to escalate privileges or gather intelligence for further attacks.

CWE-281Improper Preservation of Permissions (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (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 10 Jul 2025, 22:34 UTC

WeaknessesCWE-281

Technical details

References

Community reviews

Related threats