CVE-2026-124021

waiting for further signalsZero needs more public information before it can validate it.

GHSA-mgcx-hxxw-4q57 ↗EUVD-2026-125803 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Control Web Panel < 1.30.6
fixed in 1.30.6
CWE-863 Incorrect Authorization
ETK-2026-4432Zero's internal tracking ID, independent of the CVE number., permanent identifier
9h 04msince last run
56mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h11m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Control Web Panel versions earlier than 1.30.6 have an API authorization bypass. An attacker who has a password-recovery token and can satisfy the legacy-signature condition may gain API access to create account-level scheduled commands or retrieve sensitive account records.

mitigation

Upgrade Control Web Panel to version 1.30.6 or later. Restrict access to the affected API endpoints until the upgrade is complete.

fixed in 1.30.6

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
56m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 21:43Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-13 21:43Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-124021

{
  "etk_id": "ETK-2026-4432",
  "cve_id": "CVE-2026-124021",
  "display_id": "CVE-2026-124021",
  "ghsa_id": "GHSA-mgcx-hxxw-4q57",
  "euvd_id": "EUVD-2026-125803",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Control Web Panel API",
  "summary": "Control Web Panel versions earlier than 1.30.6 have an API authorization bypass. An attacker who has a password-recovery token and can satisfy the legacy-signature condition may gain API access to create account-level scheduled commands or retrieve sensitive account records.",
  "mitigation": "Upgrade Control Web Panel to version 1.30.6 or later. Restrict access to the affected API endpoints until the upgrade is complete.",
  "vendor": "Control Web Panel",
  "product": "Control Web Panel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.30.6"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.30.6"
      ],
      "package_name": "Control Web Panel",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 56.08966986666667,
  "t0_at": "2026-11-13T21:43:13.762000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T21:43:13.762000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T21:43:13.762000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-124021"
    }
  }
}

published 2026-11-13 21:58Z
last change 2026-11-14 07:41Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.