# CVE-2026-40102: Plane: ORM Field Reference Injection via `segment` Parameter in Saved Analytics

> Authenticated users can exploit ORM injection in saved analytics to read sensitive data like password hashes and API tokens.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-93x3-ghh7-72j3

## What is CVE-2026-40102?

CVE-2026-40102 is a medium-severity vulnerability in makeplane plane, published on 20 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Plane is an open-source project management tool. In versions 1.3.0 and below, SavedAnalyticEndpoint passes the user-controlled segment query parameter directly to a Django F() expression without validation (unlike the regular AnalyticsEndpoint, which checks against an allowlist), causing ORM Field Reference Injection. An authenticated workspace MEMBER can send GET /api/workspaces/<slug>/saved-analytic-view/<analytic_id>/ with a crafted segment value that is forwarded into build_graph_plot() and traverses foreign-key relationships (e.g. workspace__owner__password) before being projected via .values("dimension", "segment"), returning the referenced field values directly in the JSON response. This exposes sensitive data such as bcrypt password hashes, API tokens, and related users' email addresses, making it a stronger primitive than the related order_by injection where values are only leaked through ordering. This issue has been fixed in version 1.3.1.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-40102?

It affects 1 product.


Products: Plane Plane.

## How do I fix CVE-2026-40102?

No fix has been published for CVE-2026-40102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40102 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40102 exists.

## Other vulnerabilities in makeplane plane

- [CVE-2024-47830](https://insights.sbomify.com/CVE-2024-47830/): Plane allows server side request forgery via /_next/image endpoint (critical 9.3)
- [CVE-2026-30242](https://insights.sbomify.com/CVE-2026-30242/): Plane: SSRF via Incomplete IP Validation in Webhook URL Serializer (high 8.5)
- [CVE-2026-46558](https://insights.sbomify.com/CVE-2026-46558/): Missing authorization in plane (high 8.3)
- [CVE-2026-39843](https://insights.sbomify.com/CVE-2026-39843/): Plane has a Server-Side Request Forgery (SSRF) in Favicon Fetching (high 7.7)
- [CVE-2026-27706](https://insights.sbomify.com/CVE-2026-27706/): Plane Vulnerable to Full Read SSRF via Favicon Fetching in "Add Link" Feature (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40102 and fix it if it is affected.

What it is: CVE-2026-40102 is a medium-severity vulnerability in makeplane plane, published on 20 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40102 exists.

Affected product: makeplane plane. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40102/ (Markdown: https://insights.sbomify.com/CVE-2026-40102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40102
- OSV: https://osv.dev/vulnerability/CVE-2026-40102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40102/
Summaries are generated and may contain mistakes; the official description above is the record.