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

Back
New CVE Detected

CVE-2026-105638 – Authentication Bypass via Magic-Code Brute Force – Plane < 1.4.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-105638 is a critical authentication vulnerability in Plane, the open-source project management platform, affecting versions prior to 1.4.0. The magic-code (email OTP) sign-in and sign-up verification endpoints lacked any per-code failed-attempt tracking and bypassed Django REST Framework’s built-in rate throttling, allowing an unauthenticated attacker who knows a victim’s email address to brute-force the six-digit login code within its validity window and take over the account. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The magic-code verifier endpoint had no counter to track failed code-guess attempts — an incorrect submission did not increment a failure count, invalidate the associated Redis entry, or lock the target email address.
  • Throttling bypass: The vulnerable views extended Django’s base View class instead of DRF’s APIView, which meant DRF’s AuthenticationThrottle/rate-limiting logic never executed for these endpoints; no equivalent middleware-level rate limiting existed as a backstop.
  • Trigger conditions: An attacker only needs a target’s email address. The six-digit numeric code space (~900,000 possible values) combined with a multi-minute token TTL and no attempt cap made exhaustive guessing within the code’s lifetime feasible.
  • Attack vector: Network, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: Successful exploitation allows full account takeover via the magic-link login flow, bypassing password and any configured authentication protections tied to that flow, resulting in high confidentiality and integrity impact.

Affected software

  • Plane (makeplane/plane) — all versions prior to 1.4.0

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade self-hosted Plane instances to version 1.4.0 or later, which introduces a per-token attempt cap (maximum of 5 incorrect code submissions before the token is invalidated), atomic Redis-backed counting to prevent race-condition bypass, and rate limiting applied to the magic-code verification and redirect-flow authentication endpoints.
  • If immediate patching is not possible: Disable magic-link/email-OTP login as an authentication method where feasible, and restrict network exposure of the authentication endpoints (e.g., via WAF rate-limiting rules on the magic-code verify path) until the upgrade can be applied.
  • Review authentication logs for abnormal volumes of magic-code verification requests against the same account, which may indicate attempted exploitation.

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