Skip to main content
VulnerabilityPublished

CVE-2026-104968: makeplane plane · Missing Authorization

Affects makeplane planeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.4.0 soon.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade plane and makeplane/plane to 1.4.0.

Affected software

ProductAffectedFixed in
makeplaneplaneAffected
  • <1.4.0
Fixed in
  • 1.4.0
GitHubmakeplane/planepkg:github/makeplane/planeOther threatsAffected
  • <1.4.0
Fixed in
  • 1.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Plane to version 1.4.0 or later, where this missing authorization check has been fixed. Since this is an open-source project and no cloud service is involved, manual patching or upgrading is required. Patch status is confirmed fixed in 1.4.0. No additional mitigations are indicated by the vendor.

Description

Plane, an open-source project management tool, has a missing authorization vulnerability prior to version 1.4.0. An authenticated user who knows a workspace slug can access workspace member information and project member data via a specific API endpoint, even if they are not a member of that workspace. This issue is due to the lack of workspace-membership checks in the API's permission implementation. The vulnerability is fixed in version 1.4.0.

References

Community reviews

Loading reviews…