CVE-2026-105641: CWE-798: Use of Hard-coded Credentials in makeplane plane
Description
Plane, an open-source project management tool, had hard-coded secret keys in certain deployment manifests prior to version 1.4.0. These fixed, publicly known SECRET_KEY and LIVE_SERVER_SECRET_KEY values were active if operators did not override them, allowing attackers to forge Django-signed values and bypass live-service authentication. This vulnerability is addressed in version 1.4.0.
CVSS v3.1
Score 9.8critical
Affected software
makeplane
plane
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-105641 describes a critical vulnerability in Plane versions prior to 1.4.0 where the deployments/aio/community/ and deployments/cli/community/ manifests include fixed, publicly known SECRET_KEY and LIVE_SERVER_SECRET_KEY defaults. Operators who did not override these secrets left deployments exposed. The SECRET_KEY is used by Django to sign values, so knowledge of it allows attackers to forge signed data and compromise accounts or sessions. The LIVE_SERVER_SECRET_KEY enables bypass of live-service authentication on unchanged community deployments. The setup.sh script only randomizes secrets for the development Docker Compose path, leaving production community deployments vulnerable. This issue is fixed in Plane 1.4.0.
Potential Impact
Attackers with knowledge of the hard-coded SECRET_KEY can forge Django-signed values, leading to account or session compromise. Knowledge of the LIVE_SERVER_SECRET_KEY allows bypassing live-service authentication on affected community deployments. This results in full compromise potential with high confidentiality, integrity, and availability impact, as reflected by the CVSS 3.1 score of 9.8 (critical).
Mitigation Recommendations
Upgrade Plane to version 1.4.0 or later, where this issue is fixed by removing hard-coded secrets and properly randomizing them. Operators should ensure that SECRET_KEY and LIVE_SERVER_SECRET_KEY values are overridden from defaults in any deployment. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-05T16:40:39.612Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac3ed982cdf04f6562b656e
Added to database: 10/05/2026, 18:34:00 UTC
Last enriched: 10/05/2026, 18:48:20 UTC
Last updated: 10/05/2026, 18:56:34 UTC
Views: 10
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.