Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged Nextcloud user
-
DeliveryContinuously send SSRF requests at recording backend
-
ExploitVictim starts whiteboard recording
-
ExecutionLeak victim JWT via internal Chrome DevTools Protocol
-
ImpactGain read/write access to victim's whiteboard
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must hold a low-privileged authenticated account (PR:L) on a Nextcloud instance that has the Whiteboard app with its recording feature in use. Exploitation depends on a victim starting a recording - the recording backend invokes a headless Chrome instance exposing the Chrome DevTools Protocol, and the SSRF reaches that internal CDP API to leak the victim's JWT (UI:R, passive victim action). Limiting factors: requires valid credentials on the same instance, requires the recording feature to be deployed and actively used, requires the attacker to continually poll/exploit to catch the token at the moment of recording, and impact is scoped to the victim's whiteboard (read/write) rather than full account compromise. |
| Impact | This is a medium-severity issue (CVSS 4.6) whose signals point to a targeted, conditional attack rather than a widespread, easily-weaponized one. The CVSS 3.0 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N) shows network reach but requires an authenticated low-privileged account (PR:L) and victim user interaction (UI:R) - specifically the victim starting a recording - which materially constrains real-world exploitability. No EPSS score and no KEV listing are present in the input, so there is no evidence of active exploitation or high predicted exploitation probability; absence of these is not itself reassurance, but combined with the UI/privilege requirements it suggests this is not a mass-exploitable flaw. A public PoC reference exists (a HackerOne report) but it is not verified as working exploit code, so POC availability should not be treated as confirmed active exploitation - these are distinct signals. The vuln.today decision label is 'this_month', indicating a patch-on-normal-cadence priority rather than an emergency. Net: a legitimate but moderate priority - worth patching within the vendor's maintenance window, driven by the confidentiality/integrity impact on another user's whiteboard, not by evidence of broad exploitation. |
| Exploit ScenarioDerived | A low-privileged authenticated user on a shared Nextcloud instance running the Whiteboard app repeatedly issues SSRF requests (CWE-918) that reach the internal Chrome DevTools Protocol API used by the whiteboard recording backend. When a victim starts a recording, the attacker captures the victim's leaked JWT authentication token and uses it to gain read/write access to the victim's whiteboard. A HackerOne report reference exists but is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Server-side request forgery in the Nextcloud Whiteboard app lets an authenticated low-privileged user force the recording backend to reach an internal Chrome DevTools Protocol API and leak another user's JWT authentication token, granting read/write access to that victim's whiteboard. The attacker must hold a valid account on the same Nextcloud instance and repeatedly poll the SSRF while a victim starts a recording, so the victim's own action is a prerequisite (UI:R) and successful capture is timing-dependent. Scored 4.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N) and rated this_month by vuln.today; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, so the realistic risk is targeted, conditional abuse rather than mass scanning.
RemediationAI
Vendor patch: patch availability is confirmed from the vendor side, but no exact fixed version string accompanies this record, so confirm the corrected Whiteboard release in the vendor advisory and the HackerOne report at https://hackerone.com/reports/3576823 before upgrading, then apply it to every Nextcloud instance running the Whiteboard app. Where patching must wait, the attack path depends on the recording feature being deployed and actively used, so disabling or not enabling Whiteboard recording removes the headless-Chrome/DevTools exposure that the SSRF traverses; the trade-off is loss of recording functionality for all users on the instance. Note that this does not address the underlying SSRF handling, and the vendor's fix remains the complete remedy. Because exploitation requires only a low-privileged account and is repeated until a victim starts a recording, review instance logs for unusual outbound requests from the Whiteboard/recording backend to loopback or internal DevTools ports as a detection measure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-918 server-side request forgery: the Whiteboard app's recording component runs a headless Chrome instance whose Chrome DevTools Protocol endpoint is reachable from the application's own network position but is not intended to be reachable by tenant users. By supplying a crafted request that the backend follows, an attacker reaches that internal CDP API and reads state that includes the JWT authentication token belonging to the user whose recording session is active, since the browser context used for recording is authenticated as that user. Possession of the JWT then lets the attacker act as the victim against the Whiteboard service only, yielding read/write on that victim's boards rather than broad account takeover. The exposure is bounded by deployment: it exists only where the recording feature is installed and actually used, and it requires a valid low-privileged account on the same instance (PR:L), network reachability (AV:N), and a victim initiating a recording (UI:R). CPE data identifies the affected component as nextcloud:whiteboard; the underlying Nextcloud server itself is not the flawed component.
Know when Whiteboard gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Network SSRF needs a low-privileged account (PR:L) and depends on the victim starting a recording (UI:R); impact is limited to leaking a JWT (C:L) and gaining whiteboard read/write (I:L), with no availability effect.
Primary rating from Vendor (hackerone).
CVSS VectorVendor: hackerone
Lifecycle Timeline
2DescriptionCVE.org
A SSRF vulnerability found that enables access to internal Chrome Devtools Protocol APIs that can leak the JWT authentication token for another user. A low privileged attacker could continually exploit this vulnerability to leak the JWT authentication token for another user when they start a recording, which then enables the attacker read/write access to the victim's Whiteboard.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
EUVD-2026-111132
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB