Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102988 Overview
Plane is an open-source project management tool affected by an Object-Relational Mapping (ORM) injection flaw prior to version 1.4.0. Multiple issue-listing endpoints, including unauthenticated public deploy boards handled by IssueListSpaceEndpoint in apps/api/plane/space/views/issue.py, pass a user-controlled order_by parameter to Django's order_by method without allowlist validation. Attackers can abuse double-underscore relationship traversal to reference arbitrary related model fields. This exposes database schema details through error messages and may disclose field values through differential ordering [CWE-943]. The issue is fixed in version 1.4.0.
Critical Impact
Unauthenticated attackers can enumerate internal database schema and infer sensitive field values on public deploy boards by manipulating the order_by query parameter.
Affected Products
- Plane (makeplane/plane) versions prior to 1.4.0
- Self-hosted Plane deployments exposing public deploy boards
- Plane API endpoints using order_issue_queryset in apps/api/plane/utils/order_queryset.py
Discovery Timeline
- 2026-10-13 - CVE CVE-2026-102988 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-102988
Vulnerability Analysis
The vulnerability is a control-of-dynamically-managed code resources flaw [CWE-943] in Plane's queryset ordering logic. Issue-listing endpoints accept an order_by request parameter and forward it directly to Django's queryset order_by method. The helper order_issue_queryset in apps/api/plane/utils/order_queryset.py does not validate the parameter against an allowlist of permitted sortable fields.
Because Django's ORM supports double-underscore relationship traversal (for example, author__email), an attacker can chain arbitrary related model fields through the sort parameter. Invalid traversals surface detailed error messages that expose model names, field names, and relationship structure. Even when queries succeed, differential ordering can leak values of otherwise unexposed fields via a binary-search-style oracle.
Root Cause
The root cause is missing input validation. The sort parameter is treated as trusted user input and passed to the ORM without an allowlist check. The IssueListSpaceEndpoint endpoint compounds the exposure because it is unauthenticated and reachable on public deploy boards.
Attack Vector
The attack is remote, network-based, and requires no authentication or user interaction. An attacker crafts HTTP requests to a public deploy board or other issue-listing endpoint with a malicious order_by value that traverses related models. Repeated requests allow the attacker to map the schema and infer sensitive values from ordering behavior.
# Security patch - apps/api/plane/api/views/issue.py
from plane.utils.path_validator import sanitize_filename
from plane.utils.order_queryset import ACTIVITY_ORDER_BY_ALLOWLIST, sanitize_order_by
from plane.bgtasks.storage_metadata_task import get_asset_object_metadata
# Security patch - apps/api/plane/api/views/cycle.py
from plane.utils.cycle_transfer_issues import transfer_cycle_issues
from plane.utils.order_queryset import ISSUE_ORDER_BY_ALLOWLIST, sanitize_order_by
from plane.utils.host import base_host
Source: GitHub Commit cc3eb974. The patch introduces explicit allowlists (ISSUE_ORDER_BY_ALLOWLIST, ACTIVITY_ORDER_BY_ALLOWLIST) and a sanitize_order_by helper that rejects any field not on the allowlist.
Detection Methods for CVE-2026-102988
Indicators of Compromise
- HTTP requests to Plane issue-listing endpoints containing order_by values with double-underscore relationship traversal (for example, order_by=created_by__email).
- Repeated requests to IssueListSpaceEndpoint on public deploy boards from a single source iterating over field names.
- Application error responses containing Django FieldError or model-name strings returned to external clients.
Detection Strategies
- Inspect web server and application logs for order_by query parameters containing __ sequences or references to fields outside the expected sort set.
- Alert on high-volume access to /spaces/ deploy board endpoints with varying order_by values from the same client.
- Correlate 400/500 responses from Plane API routes with the presence of a non-empty order_by parameter.
Monitoring Recommendations
- Enable verbose request logging on reverse proxies fronting Plane and retain query strings for forensic review.
- Add a WAF rule flagging order_by parameters that contain __ relationship traversal patterns.
- Monitor Plane API error rates for sudden spikes that may indicate schema enumeration.
How to Mitigate CVE-2026-102988
Immediate Actions Required
- Upgrade Plane to version 1.4.0 or later, which introduces the sanitize_order_by allowlist control.
- Audit public deploy boards and restrict exposure of IssueListSpaceEndpoint where business requirements allow.
- Review application logs for prior exploitation attempts referencing order_by with double-underscore syntax.
Patch Information
The fix is included in Plane release v1.4.0 via Pull Request #9292 and commit cc3eb974. Additional context is published in the GitHub Security Advisory GHSA-2r95-c453-vxmr.
Workarounds
- Deploy a WAF or reverse proxy rule that strips or rejects order_by parameters containing __ or values outside a known-good set.
- Disable public deploy boards until upgrade is complete to remove the unauthenticated attack surface.
- Suppress detailed Django error responses in production by ensuring DEBUG=False and generic error handlers.
# Example nginx rule to block order_by relationship traversal
if ($arg_order_by ~* "__") {
return 400;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

