CVE-2026-27705: CWE-639: Authorization Bypass Through User-Controlled Key in makeplane plane
CVE-2026-27705 is an authorization bypass vulnerability in the open-source project management tool Plane versions prior to 1. 2. 2. The flaw exists in the ProjectAssetEndpoint. patch() method, which allows authenticated users, including those with minimal privileges like GUEST, to modify attributes of any asset across all workspaces and projects by guessing asset UUIDs. This occurs because the method performs a global asset lookup by asset ID without verifying workspace or project ownership. Exploitation requires no user interaction and no elevated privileges beyond authentication. The vulnerability has a CVSS score of 4. 9 (medium severity) and was fixed in Plane version 1. 2.
AI Analysis
Technical Summary
The vulnerability CVE-2026-27705 affects Plane, an open-source project management tool, in versions prior to 1.2.2. The issue lies in the ProjectAssetEndpoint.patch() method located in the file apps/api/plane/app/views/asset/v2.py (lines 579–593). This method performs a global lookup of assets using only the asset ID (primary key) via FileAsset.objects.get(id=pk) without verifying that the asset belongs to the workspace and project specified in the URL path. Consequently, any authenticated user, including those assigned the GUEST role, can modify the 'attributes' and 'is_uploaded' status of assets belonging to any workspace or project within the Plane instance by guessing or enumerating asset UUIDs. This represents an authorization bypass vulnerability categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). The flaw allows unauthorized modification of project assets, undermining data integrity and potentially disrupting project workflows. The vulnerability does not require elevated privileges beyond authentication and does not need user interaction, making it easier to exploit. The issue was addressed and fixed in Plane version 1.2.2 by adding proper ownership verification during asset lookup to ensure that asset modifications are restricted to the correct workspace and project context.
Potential Impact
The primary impact of this vulnerability is unauthorized modification of project assets across all workspaces and projects within a Plane instance. This can lead to data integrity issues, as malicious or unauthorized users can alter asset attributes or upload status, potentially corrupting project data or causing confusion among legitimate users. For organizations relying on Plane for project management, this could disrupt collaboration, delay project timelines, and erode trust in the platform's security controls. Although the vulnerability does not allow asset deletion or access to asset content directly, the ability to modify asset metadata can be leveraged for further attacks or social engineering. Since any authenticated user can exploit this, including those with minimal privileges, insider threats or compromised low-privilege accounts pose a significant risk. The vulnerability does not affect availability directly but can indirectly impact operational efficiency and data reliability.
Mitigation Recommendations
Organizations should upgrade all Plane instances to version 1.2.2 or later, where the vulnerability is fixed by enforcing proper ownership verification during asset modification requests. Until upgrades are applied, administrators should restrict user authentication to trusted personnel only and monitor asset modification logs for suspicious activity, especially modifications originating from low-privilege accounts. Implement network segmentation and access controls to limit exposure of the Plane application to only necessary users. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unusual asset modification attempts or enumeration of asset UUIDs. Regularly audit user roles and permissions to ensure minimal privilege principles are enforced. Finally, educate users about the risks of credential compromise and enforce strong authentication mechanisms to reduce the risk of unauthorized access.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, Japan, South Korea, India
CVE-2026-27705: CWE-639: Authorization Bypass Through User-Controlled Key in makeplane plane
Description
CVE-2026-27705 is an authorization bypass vulnerability in the open-source project management tool Plane versions prior to 1. 2. 2. The flaw exists in the ProjectAssetEndpoint. patch() method, which allows authenticated users, including those with minimal privileges like GUEST, to modify attributes of any asset across all workspaces and projects by guessing asset UUIDs. This occurs because the method performs a global asset lookup by asset ID without verifying workspace or project ownership. Exploitation requires no user interaction and no elevated privileges beyond authentication. The vulnerability has a CVSS score of 4. 9 (medium severity) and was fixed in Plane version 1. 2.
AI-Powered Analysis
Technical Analysis
The vulnerability CVE-2026-27705 affects Plane, an open-source project management tool, in versions prior to 1.2.2. The issue lies in the ProjectAssetEndpoint.patch() method located in the file apps/api/plane/app/views/asset/v2.py (lines 579–593). This method performs a global lookup of assets using only the asset ID (primary key) via FileAsset.objects.get(id=pk) without verifying that the asset belongs to the workspace and project specified in the URL path. Consequently, any authenticated user, including those assigned the GUEST role, can modify the 'attributes' and 'is_uploaded' status of assets belonging to any workspace or project within the Plane instance by guessing or enumerating asset UUIDs. This represents an authorization bypass vulnerability categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). The flaw allows unauthorized modification of project assets, undermining data integrity and potentially disrupting project workflows. The vulnerability does not require elevated privileges beyond authentication and does not need user interaction, making it easier to exploit. The issue was addressed and fixed in Plane version 1.2.2 by adding proper ownership verification during asset lookup to ensure that asset modifications are restricted to the correct workspace and project context.
Potential Impact
The primary impact of this vulnerability is unauthorized modification of project assets across all workspaces and projects within a Plane instance. This can lead to data integrity issues, as malicious or unauthorized users can alter asset attributes or upload status, potentially corrupting project data or causing confusion among legitimate users. For organizations relying on Plane for project management, this could disrupt collaboration, delay project timelines, and erode trust in the platform's security controls. Although the vulnerability does not allow asset deletion or access to asset content directly, the ability to modify asset metadata can be leveraged for further attacks or social engineering. Since any authenticated user can exploit this, including those with minimal privileges, insider threats or compromised low-privilege accounts pose a significant risk. The vulnerability does not affect availability directly but can indirectly impact operational efficiency and data reliability.
Mitigation Recommendations
Organizations should upgrade all Plane instances to version 1.2.2 or later, where the vulnerability is fixed by enforcing proper ownership verification during asset modification requests. Until upgrades are applied, administrators should restrict user authentication to trusted personnel only and monitor asset modification logs for suspicious activity, especially modifications originating from low-privilege accounts. Implement network segmentation and access controls to limit exposure of the Plane application to only necessary users. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unusual asset modification attempts or enumeration of asset UUIDs. Regularly audit user roles and permissions to ensure minimal privilege principles are enforced. Finally, educate users about the risks of credential compromise and enforce strong authentication mechanisms to reduce the risk of unauthorized access.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-23T17:56:51.202Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 699f5b59b7ef31ef0b4d0f11
Added to database: 2/25/2026, 8:28:09 PM
Last enriched: 2/25/2026, 8:41:02 PM
Last updated: 2/25/2026, 9:29:47 PM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27730: CWE-918: Server-Side Request Forgery (SSRF) in esm-dev esm.sh
HighCVE-2026-22866: CWE-347: Improper Verification of Cryptographic Signature in ensdomains ens-contracts
LowCVE-2026-0542: CWE-653: Improper Isolation or Compartmentalization in ServiceNow ServiceNow AI Platform
CriticalCVE-2026-3192: Improper Authentication in Chia Blockchain
MediumCVE-2026-3189: Server-Side Request Forgery in feiyuchuixue sz-boot-parent
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.