CVE-2026-104964: makeplane plane · Insecure Direct Object Reference
Affects makeplane planeSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.4.0 when convenient.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade plane and makeplane/plane to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| makeplaneplane | Affected
| Fixed in
|
GitHubmakeplane/planepkg:github/makeplane/planeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Plane version 1.4.0. Users should upgrade to version 1.4.0 or later to remediate this issue. No additional mitigation is indicated or required beyond applying the official fix.
Description
Plane, an open-source project management tool, had a vulnerability prior to version 1.4.0 where its project update endpoint authorized users based on the workspace slug but loaded projects globally by UUID without workspace binding. This allowed administrators of one workspace to modify projects in other workspaces if they knew the project UUID, violating tenant isolation. The issue was fixed in version 1.4.0.