CVE-2026-30244
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPlane is an an open-source project management tool. Prior to version 1.2.2, unauthenticated attackers can enumerate workspace members and extract sensitive information including email addresses, user roles, and internal identifiers. The vulnerability stems from Django REST Framework permission classes being incorrectly configured to allow anonymous access to protected endpoints. This issue has been patched in version 1.2.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Plane versions prior to 1.2.2, Django REST Framework permission classes were misconfigured, allowing unauthenticated access to protected API endpoints that should have required authentication. Attackers could enumerate workspace members and extract sensitive information including email addresses, user roles, and internal identifiers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Plane versionCheck your Plane installation's version number. This is typically visible in the UI footer, in the admin panel, or by querying the application's backend (e.g., checking the Docker image tag, Helm chart version, or package.json if self-hosted).Affected if The installed version is earlier than 1.2.2 (any version < 1.2.2).
-
Identify member enumeration API endpointsLocate the API endpoints that handle workspace member listing. Common patterns include endpoints with paths like /api/v1/workspaces/{workspace_id}/members/ or /api/workspaces/{slug}/members. These are typically used to retrieve a list of members within a workspace.Affected if These endpoints exist in your Plane deployment and are part of the Django REST Framework API.
-
Test unauthenticated access to member endpointsSend an HTTP GET request to the identified member enumeration endpoints WITHOUT including any authentication headers (such as Authorization tokens or session cookies). Use a tool like curl or a browser's developer console to make the request.Affected if The endpoint returns a 200 OK response with member data (including email addresses, user roles, or internal identifiers) instead of returning 401 Unauthorized or 403 Forbidden.
-
Verify sensitive data exposureExamine the response from the unauthenticated request. Check if it exposes any of the following: user email addresses, user roles within the workspace, internal user identifiers, or other personal information.Affected if The API response contains any sensitive user information (emails, roles, internal IDs) without requiring authentication.
You are affected if your Plane version is earlier than 1.2.2 AND the workspace member enumeration API endpoints are accessible without any authentication credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.2
Upgrade Plane to version 1.2.2 or later. If immediate upgrade is not possible, review and fix the Django REST Framework permission class configuration to ensure all member enumeration endpoints require proper authentication.
1.2.2
- Backup your current Plane installation and database before proceeding with the upgrade
- Stop the Plane service
- Upgrade Plane to version 1.2.2 using your deployment method (e.g., Docker pull, package manager, or source upgrade)
- Restart the Plane service
- Verify the upgrade was successful by checking the version number
- Test that unauthenticated requests to member enumeration endpoints are now properly restricted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30244 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data