CVE
Control Web Panel authorization bypass in remote API
Affects Control Web Panel (CWP) before 1.30.6, identified by webpanel_version. Fixed in 1.30.6. No vendor severity rating is given, only the CVSS score of 9.2 (critical).
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 1.30.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.30.6.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Control Web Panel (CWP) versions before the fixed release contain an authorization bypass in its remote API that can be reached over the network without logging in. An attacker holding a password-recovery token and a predictable legacy signature can add arbitrary cron commands to run as the affected hosting account, and can also read account usernames, contact emails, and password hashes.
Original description
Control Web Panel (CWP) before webpanel_version 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.
Who should check
Teams running Control Web Panel (CWP) versions before 1.30.6 on Linux hosting servers
“Control Web Panel (CWP) before webpanel_version 1.30.6”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.30.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124021 (Control Web Panel < 1.30.6 Authorization Bypass via oauth_authorization_codes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-124021 (entry last updated 2026-11-13):
Affected:
- Control Web Panel Control Web Panel: fixed in 1.30.6
Fixed versions: 1.30.6.
Conditions (all must be true for the bug to be hit):
- Control Web Panel before 1.30.6 (webpanel_version before 1.30.6). (source: https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes)
- Attacker must hold a password-recovery token and a predictable legacy signature. (source: https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-124021 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124021 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://control-webpanel.com/changelog
- https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-124021
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124021"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Control Web Panel Control Web Panel
fixed in 1.30.6
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124021
Is CVE-2026-124021 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw is an authorization bypass in CWP's oauth_authorization_codes handling. The facts say an attacker needs a password-recovery token and a predictable legacy signature, and could then add arbitrary cron commands to run as the affected hosting account. The same route also exposes usernames, contact emails and password hashes through global account routes.Source: vulncheck.com
Which versions are affected by CVE-2026-124021?
Control Web Panel: before 1.30.6.Source: cve.now feed data
Am I affected, and how do I check?
Control Web Panel versions before 1.30.6 are in scope. To check a server, look at the webpanel_version value in the installed CWP. The advisory describes the setup as requiring a password-recovery token and a predictable legacy signature.Source: vulncheck.com
How do I fix CVE-2026-124021?
Upgrade Control Web Panel to 1.30.6 or later, which is the fixed version listed for this vulnerability. The facts name no workaround or patch identifiers.Source: vulncheck.com