CVE-2026-124021: Control Web Panel < 1.30.6 Authorization Bypass via oauth_authorization_codes

Q: Which installations are affected?

Control Web Panel installations with webpanel_version earlier than 1.30.6 are affected. The provided information does not state whether any particular deployment configuration avoids exposure.

Q: What does an attacker need to exploit this issue?

An attacker needs a password-recovery token and a predictable legacy signature. They do not need a proper remote-API key to obtain remote-API authorization through the vulnerable validation logic.

Q: What access can exploitation provide?

An attacker can use POST /cronjobsusers/ to add arbitrary cron commands, resulting in command execution as the affected hosting account. The same token can also be used to access global account-list and account-detail routes that expose usernames, contact email addresses, and password hashes.

Published Nov 13, 2026

Updated

Control Web Panel (CWP) before webpanelversion 1.30.6 contains an authorization bypass vulnerability in the validate() function of api/v1/index.php that allows attackers holding a password-recovery token and a predictable legacy signature to obtain valid remote-API authorization without a proper API key. Attackers can exploit this flaw via the POST /cronjobsusers/ endpoint to add arbitrary cron commands and achieve command execution as the affected hosting account, and can also abuse the same token to access global account-list and account-detail routes exposing usernames, contact emails, and password hashes.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Control Web Panel to a version that resolves this vulnerability.
Fixed in 1.30.6

Event History

Nov 13, 2026

CVE Published

via MITRE·09:43 PM

Data Sourced

via MITRE·09:43 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·10:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Which installations are affected?

Control Web Panel installations with webpanel_version earlier than 1.30.6 are affected. The provided information does not state whether any particular deployment configuration avoids exposure.

What does an attacker need to exploit this issue?

An attacker needs a password-recovery token and a predictable legacy signature. They do not need a proper remote-API key to obtain remote-API authorization through the vulnerable validation logic.

What access can exploitation provide?

An attacker can use POST /cronjobsusers/ to add arbitrary cron commands, resulting in command execution as the affected hosting account. The same token can also be used to access global account-list and account-detail routes that expose usernames, contact email addresses, and password hashes.