CVE-2024-52519 [Low] | Security Vulnerability in Nextcloud Server

Nextcloud Server is a self hosted personal cloud system. The OAuth2 client secrets were stored in a recoverable way, so that an attacker that got access to a backup of the database and the Nextcloud config file, would be able to decrypt them. It is recommended that the Nextcloud Server is upgraded to 28.0.10 or 29.0.7 and Nextcloud Enterprise Server is upgraded to 27.1.11.8, 28.0.10 or 29.0.7.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	1.34%	0.49%	-0.85%
2	2026-04-06	0.99%	1.34%	+0.35%
3	2026-03-04	—	0.99%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

1.34%

0.49%

-0.85%

2026-04-06

0.99%

1.34%

+0.35%

2026-03-04

—

0.99%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.7	3.1	LOW	`CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:P) Hands-on access—USB, keyboard, opening the case—not something you do purely over the wire. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	0.1	2.5	[email protected]
8.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

2.7

3.1

LOW

CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N Click to expand

Attack vector (AV:P): Hands-on access—USB, keyboard, opening the case—not something you do purely over the wire.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

0.1

2.5

[email protected]

8.2

3.1

HIGH

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

4.2

[email protected]

Affected software / configurations for CVE-2024-52519

Vendor	Product	Version	Raw CPE
nextcloud	nextcloud_server	>= 27.0.0, < 27.1.11.8	cpe:2.3:a:nextcloud:nextcloud_server:::::enterprise:::*
nextcloud	nextcloud_server	>= 28.0.0, < 28.0.10	cpe:2.3:a:nextcloud:nextcloud_server:::::-:::*
nextcloud	nextcloud_server	>= 28.0.0, < 28.0.10	cpe:2.3:a:nextcloud:nextcloud_server:::::enterprise:::*
nextcloud	nextcloud_server	>= 29.0.0, < 29.0.7	cpe:2.3:a:nextcloud:nextcloud_server:::::-:::*
nextcloud	nextcloud_server	>= 29.0.0, < 29.0.7	cpe:2.3:a:nextcloud:nextcloud_server:::::enterprise:::*

References for CVE-2024-52519

URL	Tags
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-fvpc-8hq6-jgq2	Vendor Advisory
https://github.com/nextcloud/server/commit/09b8aea8f6783514bffe00df6abbf9fa542faac5	Patch
https://github.com/nextcloud/server/pull/47635	Issue Tracking

URL

CVE-2024-52519 | Nextcloud Server's OAuth2 client secrets were stored in a recoverable way

Exploit prediction scoring system (EPSS) score for CVE-2024-52519

Common vulnerability scoring system (CVSS) metrics for CVE-2024-52519

Weakness enumeration for CVE-2024-52519

Affected software / configurations for CVE-2024-52519

References for CVE-2024-52519