Skip to main content

Nextcloud Whiteboard CVE-2026-87897

| EUVDEUVD-2026-111132 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-10-27 hackerone
4.6
CVSS 3.0 · Vendor: hackerone
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged Nextcloud user
  2. Delivery
    Continuously send SSRF requests at recording backend
  3. Exploit
    Victim starts whiteboard recording
  4. Execution
    Leak victim JWT via internal Chrome DevTools Protocol
  5. Impact
    Gain 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

whiteboard 1.0.0 <1.0.0

Affected Packages

euvd whiteboard fix: 1.0.0

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

Vendor (hackerone) PRIMARY 4.6 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
vuln.today AI 4.6 MEDIUM

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.

3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (hackerone).

CVSS VectorVendor: hackerone

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

Lifecycle Timeline

2
Patch available
Oct 27, 2026 - 17:18 EUVD
CVE Published
Oct 27, 2026 - 16:15 cve.org
MEDIUM 4.6

DescriptionCVE.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

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
optional Nextcloud add-on app with separate recording backend, limited adoption
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

23
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +23
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy