Stored XSS via unsanitized intake description
Published Jun 17, 2026 · Updated Jun 17, 2026
Stored XSS in Plane CE 1.3.1 allows remote authenticated users to execute JavaScript in a reviewer's browser via an intake work item. The API v1 intake creation path writes description_html directly to Issue.description_html, bypassing IssueSerializer.validate() and its nh3 sanitizer. Guest-level project membership and an API token suffice; execution occurs when another user reviews the stored item, exposing data or actions available in that session.
Summary
What happened
Stored XSS in Plane CE 1.3.1 allows remote authenticated users to execute JavaScript in a reviewer's browser via an intake work item. The API v1 intake creation path writes description_html directly to Issue.description_html, bypassing IssueSerializer.validate() and its nh3 sanitizer. Guest-level project membership and an API token suffice; execution occurs when another user reviews the stored item, exposing data or actions available in that session.
The record
- CVE
- CVE-2026-10850
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Plane
- Product
- Plane
- Classifications
- CWE-79, CAPEC-592, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Fluid Attacks intake description_html proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo