MEDIUM 5.4

CVE-2026-10850: Stored XSS in Plane CE 1.3.1 Intake API – Analysis & Patch Guidance

Plane CE version 1.3.1 contains a stored cross-site scripting (XSS) vulnerability in its API. A user with low-level project membership can inject malicious HTML and JavaScript code into the description field when creating intake work items through the REST API. This code is then stored and executed in the browsers of other users who view that work item, potentially allowing attackers to steal session tokens, redirect users to phishing sites, or perform actions on behalf of victims.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weaknesses (CWE)
CWE-79
Affected products
1 configuration(s)
Published / Modified
2026-06-17 / 2026-06-23

NVD description (verbatim)

Plane CE 1.3.1 allows a low-privileged project member to submit arbitrary HTML/JS in the description_html field when creating an intake work item through the API v1 intake endpoint.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-10850 is a stored XSS vulnerability (CWE-79) affecting Plane CE 1.3.1's API v1 intake endpoint. The vulnerability exists because the `description_html` parameter accepts unsanitized user input when creating intake work items. An authenticated low-privileged user can submit arbitrary HTML and JavaScript, which is persisted in the database without proper encoding or validation. When other users retrieve and display the work item in the web interface, the malicious script executes in their browser context with their privileges, enabling session hijacking, data exfiltration, or further compromise.

Business impact

This vulnerability creates operational and security risk for organizations using Plane CE for project management. If exploited, attackers with minimal project access could compromise the integrity of work items and potentially escalate access by hijacking administrator sessions. The persistence of the malicious payload means the attack affects multiple users over time without requiring repeated exploitation attempts. Teams relying on Plane CE for sensitive project data or compliance workflows face exposure of information through XSS-based exfiltration.

Affected systems

Plane Community Edition (CE) version 1.3.1 is confirmed vulnerable. Organizations running this specific version with publicly accessible or internally exposed instances are at risk, particularly if they have contractor, vendor, or multi-team access models where low-privileged users are provisioned. Verify your Plane CE version in the system administration settings or by checking the release notes of your deployment.

Exploitability

Exploitation requires valid authentication and project membership, which raises the barrier compared to unauthenticated attacks. However, the requirement is only low-privilege access—standard contributors to a project can exploit this. The attack is reliable once an attacker has user credentials or can socially engineer access, as input validation is absent. No user interaction from the attacker is required beyond submitting the malicious payload; the victim's interaction with the stored item triggers the XSS. Network accessibility is straightforward (AV:N). Overall, this is a practical post-authentication vulnerability with meaningful real-world risk in environments with permissive user provisioning.

Remediation

Upgrade Plane CE to a patched version released after 2026-06-23 that sanitizes and validates the `description_html` field on API intake endpoints. If immediate patching is not feasible, restrict API access to trusted users and implement API-level input validation or WAF rules that strip or escape HTML tags in intake creation requests. Consider disabling the public API intake endpoint if it is not operationally necessary.

Patch guidance

Check the official Plane project repository and release notes for versions after June 23, 2026. Patches should include HTML sanitization in the intake endpoint's description field processing. When patching, test intake work item creation across the API and web interface to ensure the fix does not break legitimate formatting or attachments. Recommend upgrading to the latest Plane CE stable release.

Detection guidance

Monitor API access logs for POST requests to the v1 intake endpoint with unusually large or HTML-tag-containing payloads in the `description_html` parameter. Review stored intake work items for suspicious script tags, iframe elements, or event handlers in description fields. Deploy Web Application Firewall rules to flag or block HTTP requests containing script tags in POST body parameters targeting the intake endpoint. Query your Plane database for work items containing patterns like `<script>`, `onerror=`, or `javascript:` in the description_html field to identify potentially malicious items already created.

Why prioritize this

Although listed as MEDIUM severity and not yet on CISA's KEV catalog, this vulnerability merits prompt attention because: (1) it affects a widely-used open-source project management tool with multi-tenant and contractor use cases; (2) stored XSS bypasses some perimeter defenses and affects multiple users passively; (3) exploitation is reliable with minimal privilege; (4) session hijacking and lateral movement become possible if administrators are compromised. Organizations with contractor or vendor access to Plane should prioritize patching before those with purely internal teams.

Risk score, explained

The CVSS 3.1 score of 5.4 (MEDIUM) reflects the requirement for authenticated access (PR:L) and user interaction by the victim (UI:R), which reduce the base score. However, the impact scope is changed (S:C), indicating cross-account or organizational-level concern. Confidentiality and integrity are impacted (C:L, I:L) through session hijacking and data manipulation, but availability is not affected. The moderate score should not diminish urgency in environments where low-privilege users are frequently provisioned or where project data is sensitive.

Frequently asked questions

Can an unauthenticated attacker exploit this?

No. The vulnerability requires valid project membership and authentication. An attacker must either have legitimate credentials or obtain them through credential compromise or social engineering.

Will updating Plane CE break my existing work items or integrations?

Security patches typically preserve data compatibility. Test the upgrade in a staging environment before production deployment. If you have custom integrations with the intake API, review the patch notes to ensure your API calls still work with any parameter changes.

How do I check if my Plane instance was already compromised?

Query your Plane database or review intake work item descriptions in the UI for suspicious HTML/JavaScript content like script tags, onerror handlers, or javascript: URLs. If found, isolate the instance, revoke affected user sessions, and investigate access logs for the creation timestamps and user IDs of malicious items.

Is this vulnerability exploited in the wild?

As of the publish date (June 17, 2026), this vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog, suggesting no widespread active exploitation has been reported. However, the low barrier to entry means opportunistic attackers may attempt exploitation once the CVE becomes widely known.

This analysis is based on public CVE data, vendor advisories, and CVSS scoring as of the publication date. Patch version numbers and remediation timelines should be verified against official Plane project releases and security advisories. Organizations should perform their own risk assessment relative to their deployment architecture and user access model. SEC.co does not provide warranties regarding the completeness or applicability of this guidance to specific environments. Always test patches in non-production environments before deployment. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).