CVE-2026-104967: Plane: Cross-workspace association destruction and issue mutation/read via unscoped queries in BulkDeleteIssuesEndpoint and SubIssuesEndpoint

Published Oct 5, 2026
·
Updated

Plane is an open-source project management tool. Prior to 1.4.0, BulkDeleteIssuesEndpoint and SubIssuesEndpoint in apps/api/plane/app/views/issue/ accept body- or URL-supplied issue IDs and operate on them without checking that the IDs belong to the caller's workspace and project. The permission decorator on each endpoint validates only that the caller is a member or administrator of the workspace and project named in the URL. BulkDeleteIssuesEndpoint can destroy CycleIssue and ModuleIssue associations belonging to foreign issues. SubIssuesEndpoint can re-parent foreign issues under an attacker-selected issue and return the foreign issues' metadata. This issue is fixed in 1.4.0.

Affected Software

1 affected component
Plane Plane<1.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade plane to a version that resolves this vulnerability.

    Fixed in 1.4.0

Event History

Oct 5, 2026
CVE Published
via MITRE·04:55 PM
Data Sourced
via MITRE·04:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated user who is a member or administrator of the workspace and project named in the request URL can exploit it. The user does not need permission for the workspace or project that owns the supplied foreign issue IDs.

2

What access can an attacker gain or change?

An attacker can obtain metadata for foreign issues through SubIssuesEndpoint and can re-parent those issues beneath an attacker-selected issue. They can also destroy CycleIssue and ModuleIssue associations belonging to foreign issues through BulkDeleteIssuesEndpoint.

3

Are default deployments affected?

Any Plane deployment running a version prior to 1.4.0 is affected if these endpoints are available to authenticated workspace or project members. The issue is caused by missing ownership validation for issue IDs supplied in request bodies or URLs.

4

What should be done if patching cannot happen immediately?

The provided information identifies version 1.4.0 as the fix. No temporary mitigation is specified in the available data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203