Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-105641 – Unauthenticated Remote Takeover via Hardcoded Secret Keys – Plane (Community Deplo

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-105641 is a critical use of hard-coded credentials (CWE-798) vulnerability affecting Plane, an open-source project management platform maintained by makeplane. Community (self-hosted) deployment manifests for versions prior to 1.4.0 shipped with fixed, publicly known default values for the Django SECRET_KEY and the LIVE_SERVER_SECRET_KEY, which remained active unless an operator manually overrode them. Because these keys underpin session signing and live-collaboration authentication, their disclosure allows a remote, unauthenticated attacker to forge valid sessions and bypass authentication entirely. The issue has a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The AIO (all-in-one) and CLI deployment templates for Plane hardcoded known, static values for SECRET_KEY (Django’s cryptographic signing key, used for sessions, password-reset tokens, and email confirmations) and LIVE_SERVER_SECRET_KEY (used to authorize the real-time collaboration/live-server component). These values were not randomized on install and remained active unless an operator explicitly replaced them.
  • Trigger conditions: Any Plane community/self-hosted instance deployed via the affected AIO or CLI manifests without manually rotating the default secrets.
  • Attack vector: Network, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N). An attacker who knows the publicly disclosed default SECRET_KEY can use Django’s signing utilities to forge valid session cookies, password-reset tokens, and other signed values for any account, including administrators. Separately, the disclosed LIVE_SERVER_SECRET_KEY could be used to bypass live-server access checks, reportedly validated via a plain (non-constant-time) string comparison.
  • Impact: Full compromise of confidentiality, integrity, and availability — described by the vendor as enabling unauthenticated remote takeover with complete read/write access to all workspace data, including the ability to impersonate any user such as workspace administrators.

Affected software

  • Plane (makeplane/plane) community/self-hosted deployments, versions up to and including 1.3.1
  • Specifically impacts the AIO (all-in-one) and CLI deployment manifests that embed the default SECRET_KEY and LIVE_SERVER_SECRET_KEY values
  • Fixed in version 1.4.0

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade self-hosted/community Plane deployments to version 1.4.0 or later, which removes the hardcoded defaults, generates a cryptographically random SECRET_KEY/LIVE_SERVER_SECRET_KEY on first boot, persists them across restarts, and adds startup checks that warn if a known-insecure or placeholder value is still in use.
  • If immediate patching is not possible:
    • Manually rotate SECRET_KEY and LIVE_SERVER_SECRET_KEY to unique, randomly generated values in your deployment configuration (do not rely on shipped defaults).
    • After rotating keys, invalidate existing sessions and force re-authentication for all users, since previously issued signed tokens may have been forged or are no longer valid.
    • Audit instances for signs of unauthorized access or session forgery prior to key rotation.
    • Restrict network exposure of the live-server/collaboration component where possible until keys are rotated and the instance is patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge