CVE-2023-25159 [Low] | Security Vulnerability in Nextcloud Server

Nextcloud Server is the file server software for Nextcloud, a self-hosted productivity platform, and Nextcloud Office is a document collaboration app for the same platform. Nextcloud Server 24.0.x prior to 24.0.8 and 25.0.x prior to 25.0.1, Nextcloud Enterprise Server 24.0.x prior to 24.0.8 and 25.0.x prior to 25.0.1, and Nextcloud Office (Richdocuments) App 6.x prior to 6.3.1 and 7.x prior to 7.0.1 have previews accessible without a watermark. The download should be hidden and the watermark should get applied. This issue is fixed in Nextcloud Server 25.0.1 and 24.0.8, Nextcloud Enterprise Server 25.0.1 and 24.0.8, and Nextcloud Office (Richdocuments) App 7.0.1 (for 25) and 6.3.1 (for 24). No known workarounds are available.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.20%	0.46%	+0.25%
2	2026-02-23	0.31%	0.20%	-0.10%
3	2026-02-14	—	0.31%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.20%

0.46%

+0.25%

2026-02-23

0.31%

0.20%

-0.10%

2026-02-14

—

0.31%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.3	3.1	LOW	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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:H) They need powerful rights—admin, root, or similar—before this pays off. 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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	0.8	1.4	[email protected]
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

2.3

3.1

LOW

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:H): They need powerful rights—admin, root, or similar—before this pays off.
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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

0.8

1.4

[email protected]

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

Affected software / configurations for CVE-2023-25159

Vendor	Product	Version	Raw CPE
nextcloud	nextcloud_server	>= 24.0.4, <= 24.0.8	cpe:2.3:a:nextcloud:nextcloud_server::::::::
nextcloud	nextcloud_server	24.0.2	cpe:2.3:a:nextcloud:nextcloud_server:24.0.2:-::::::
nextcloud	nextcloud_server	25.0.0	cpe:2.3:a:nextcloud:nextcloud_server:25.0.0:::::::*
nextcloud	richdocuments	>= 6.0.0, < 6.3.1	cpe:2.3:a:nextcloud:richdocuments::::::::
nextcloud	richdocuments	7.0.0	cpe:2.3:a:nextcloud:richdocuments:7.0.0:-::::::

References for CVE-2023-25159

URL	Tags
https://github.com/nextcloud/richdocuments/pull/2579	Broken Link
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-92g2-h5jv-jjmg	Vendor Advisory
https://github.com/nextcloud/server/pull/34799	Broken Link
https://hackerone.com/reports/1745755	Permissions Required Third Party Advisory

URL

CVE-2023-25159 | Nextcloud Server previews are accessible without a watermark

Exploit prediction scoring system (EPSS) score for CVE-2023-25159

Common vulnerability scoring system (CVSS) metrics for CVE-2023-25159

Weakness enumeration for CVE-2023-25159

Affected software / configurations for CVE-2023-25159

References for CVE-2023-25159