Plane
Plane: Hardcoded SECRET_KEY and LIVE_SERVER_SECRET_KEY shipped in aio/cli community deployment manifests — session forgery and live-server auth bypass
Plane is an open-source project management tool. Prior to 1.4.0, the deployments/aio/community/ and deployments/cli/community/ manifests provide fixed, publicly known SECRET_KEY and LIVE_SERVER_SECRET_KEY defaults that remain active when operators do not override them. The top-level setup.sh randomizes secrets only for the development Docker Compose path, leaving unchanged aio and cli community deployments with shared production secrets. Knowledge of SECRET_KEY enables attackers to forge Django-signed values and compromise accounts or sessions. Knowledge of LIVE_SERVER_SECRET_KEY bypasses live-service authentication on unchanged community deployments. This issue is fixed in 1.4.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.4.0
Fixed in 1.4.0
Mitigation
Upgrade plane to 1.4.0 or later.
References
- Vendor advisory github.com/makeplane/plane/security/advisories…
- Patch github.com/makeplane/plane/pull/9291
- Patch github.com/makeplane/plane/commit/1acc69e816a9…
1 more
- Release notes github.com/makeplane/plane/releases/tag/v1.4.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.