CVE-2026-105835

PLANKA 2.2.0 through 2.2.1 TOTP Brute Force via verify-totp Endpoint

Published Oct 6, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
PLANKA 2.2.0 through 2.2.1 fails to limit incorrect TOTP codes submitted to POST /api/access-tokens/verify-totp, allowing attackers to brute force two-factor authentication codes. Attackers who know a user's password can reuse the ten-minute pending token to guess six-digit codes until one succeeds, obtaining a full access token.

Analysis

AI-generated

Technical impact

The vulnerability allows an attacker who knows a user’s password to repeatedly probe a verification endpoint for the six‑digit one‑time password. Because the endpoint does not enforce any limit on incorrect attempts, an attacker can brute‑force the TOTP within the ten‑minute window of the pending token and obtain a full access token. This effectively bypasses two‑factor authentication and grants the attacker full privileges for the affected user.

Affected Systems

Versions 2.2.0 and 2.2.1 of Planka, a project management tool distributed under the planka:planka vendor label. The vulnerability is present in the verify‑totp API controller, which is part of the server side implementation of the application. No other product versions were explicitly noted.

Risk and Exploitability

With a CVSS score of 9.1 the flaw is classified as critical. The absence of an EPSS value indicates that no exploitation probability data is available, but the flaw’s nature makes it highly attractive to attackers. Because the CVE is not listed in the CISA KEV catalog, there is no known active exploitation, yet the underlying weakness (CWE-307) is a common vector for credential theft. Attackers could exploit the endpoint over the network if the application is exposed, so the attack vector is likely remote.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Planka to the latest released version that contains the TOTP verification attempt counter or is patched for this bug.
  • Add application‑level rate limiting to the /api/access-tokens/verify-totp endpoint to restrict repeated attempts.
  • Configure the backend to immediately expire or invalidate the pending token after a single successful verification or after a short timeout, preventing reuse for brute force.

Generated by OpenCVE AI on October 6, 2026 at 18:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description PLANKA 2.2.0 through 2.2.1 fails to limit incorrect TOTP codes submitted to POST /api/access-tokens/verify-totp, allowing attackers to brute force two-factor authentication codes. Attackers who know a user's password can reuse the ten-minute pending token to guess six-digit codes until one succeeds, obtaining a full access token.
Title PLANKA 2.2.0 through 2.2.1 TOTP Brute Force via verify-totp Endpoint
First Time appeared Planka
Planka planka
Weaknesses CWE-307
CPEs cpe:2.3:a:planka:planka:*:*:*:*:*:*:*:*
Vendors & Products Planka
Planka planka
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 9, 2026, 12:58 AM
Reserved
Oct 5, 2026, 10:00 PM
Status
Deferred
Published
Oct 6, 2026, 1:16 PM
Modified
Oct 9, 2026, 2:16 AM