/

CVE-2026-88895

Severity:

HIGH RISK

(7.2)

Improper Authentication (CWE-287) in CyberPanel API

CVE-2026-88895

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Two-factor authentication bypass and unauthorized administrative access

Severity:

HIGH RISK

(7.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

CyberPanel fails to consistently enforce two-factor authentication for certain API endpoints, allowing password-derived tokens to satisfy authentication requirements without a TOTP code. An attacker who obtains an administrator's password may create authenticated sessions or perform administrative operations.

Affected context

The issue occurs in CyberPanel deployments before the affected security correction when API authentication accepts password-derived tokens without independently requiring the configured TOTP factor. Risk is greatest where administrator passwords have been exposed and the API is reachable by an attacker.

Exploit preconditions

  • Attack surface: CyberPanel API endpoints
  • Required access: An administrator's password or equivalent password-derived authentication material
  • Trigger point: API authentication or authenticated-session creation
  • Why exploitation is possible: The API does not consistently enforce TOTP verification when processing password-derived tokens

Why this happens

The underlying bug is an authentication design flaw in which possession of a primary credential can substitute for an independently verified second factor. This maps to CWE-287: Improper Authentication, because the application accepts an authentication state without adequately validating all required identity factors and authorization conditions.

Potential impact

  • An attacker may create authenticated administrative sessions
  • Unauthorized users could perform privileged CyberPanel operations
  • Account, hosting, or server configuration may be modified
  • Sensitive administrative data could be accessed or altered
  • Compromised administrative access could enable further system abuse

General mitigation guidance

Mitigation generally focuses on enforcing multi-factor authentication as a mandatory, independent condition for every applicable authentication path.

Common defensive patterns include:

  • Requiring successful TOTP validation for all privileged API endpoints and session creation flows
  • Preventing password-derived tokens from bypassing second-factor checks
  • Applying consistent authentication and authorization middleware across API routes
  • Limiting administrative API exposure through network policy and access controls
  • Using short-lived, scoped tokens with secure revocation and rotation behavior
  • Applying least privilege to administrative accounts and service identities
  • Reducing reliance on password-only authentication and monitoring credential exposure

How teams detect issues like this

Organizations can detect similar weaknesses through:

  • Static and dynamic analysis of authentication middleware and token-validation paths
  • Code review checks for API routes that omit shared MFA enforcement
  • Tests that verify every privileged authentication flow rejects missing or invalid second-factor evidence
  • Monitoring for administrative sessions or API activity without corresponding TOTP verification
  • Policy enforcement requiring consistent MFA controls for privileged endpoints
  • Neutral automated security review tools that identify authentication-bypass patterns and inconsistent authorization checks

Sources

SourceLink
github.comgithub.com/usmannasir/cyberpanel/security/advisories/GHSA-h2f7-38ww-5pwc
vulncheck.comvulncheck.com/advisories/cyberpanel-before-3.0.5-authentication-bypass-via-api

Frequently asked

questions

It may be exploitable remotely when CyberPanel API endpoints are reachable and an attacker has obtained an administrator's password.

Yes. The described attack depends on deriving or using authentication material from a valid administrator password; the vulnerability bypasses the additional TOTP requirement rather than eliminating the need for a primary credential.

Require independent TOTP verification for every privileged API authentication and session-creation path, including flows that accept password-derived tokens.

Centralize MFA enforcement, test all authentication paths for factor separation, restrict administrative API exposure, and monitor privileged activity that lacks expected second-factor evidence.

Find out what's already
exploitable in your codebase.