Control Web Panel (CWP) before webpanel_version 1.16 contains an arbitrary file write and OS command injection vulnerability in the phpini_editor user panel module that allows attackers with access to the module to write attacker-controlled content to arbitrary paths and execute arbitrary OS commands. Attackers can exploit the acc=update action to write files via file_put_contents without path confinement and the acc=addlabelphpiniadv action to pass unsanitized input into shell_exec, achieving code execution in the user panel context.
CVE-2026-73697
CRITICALPre-NVD 8.89.8Trending — 6 sources updated this week
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than the CVSS score beside it.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-02. The CNA's CVSS baseline 8.8; sources differ by 1.0.
Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Also known asEUVD-2026-115229 (ENISA EUVD) · GHSA-rfph-hxj5-v269 (GitHub Security Advisories)Source: ENISA EUVD
9.8EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
- CVSS v3
- 8.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 45EG Risk 45/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation1.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule. - EPSS PROB
- 1.6%
- EPSS %ILE
- 76th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 1.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 2, 2026
Last Modified
November 3, 2026
Advisory Details (2)
Auto-updated Nov 2, 2026Fix referenced — no release confirmed yet.
Web pageMentions a patch (unverified)
Changelog – Control-WebPanel [CWP]
https://control-webpanel.com/changelogWeb page
Control Web Panel (CWP) < 1.16 File Write and Command Injection | Advisories | VulnCheck
https://www.vulncheck.com/advisories/control-web-panel-cwp-file-write-and-command-injectionVendor Advisories for CVE-2026-73697(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-03 17:12 UTCEG score recompute
- 2026-11-03 17:12 UTCGHSA enrichmentGHSA-rfph-hxj5-v269 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-03 16:49 UTCEPSS rescoreEPSS 1.6% · 76th percentile
- 2026-11-03 14:29 UTCEG score recompute
- 2026-11-03 14:29 UTCGHSA enrichmentGHSA-rfph-hxj5-v269 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-03 13:38 UTCEG score recompute
- 2026-11-03 13:38 UTCGHSA enrichmentGHSA-rfph-hxj5-v269 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-02 19:46 UTCGHSA enrichmentGHSA-rfph-hxj5-v269 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-02 16:29 UTCEG score recompute▲ 1.00
- 2026-11-02 16:29 UTCGHSA enrichmentGHSA-rfph-hxj5-v269 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-02 16:27 UTCNVD updateCVSS v3 → 8.8 · CVSS v4 → 8.7 · severity → HIGH
- 2026-11-02 16:03 UTCENISA EUVD ID recordedEUVD-2026-115229 · Source: ENISA EUVD
- 2026-11-02 15:26 UTCNVD updateCVSS v3 → 9.8 · CVSS v4 → 9.3 · severity → CRITICAL
- 2026-11-02 15:18 UTCEG score recompute▼ 1.00
- 2026-11-02 15:17 UTCMITRE cvelistV5CVSS v3 → 8.8 · CVSS v4 → 8.7 · severity → HIGH
- 2026-11-02 14:58 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
- 2026-11-02 14:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-73697?
CVE-2026-73697 is a critical-severity vulnerability; its CVE record was published on November 2, 2026. Control Web Panel (CWP) before webpanel_version 1.16 contains an arbitrary file write and OS command injection vulnerability in the phpini_editor user panel module that allows attackers with access to the module to write attacker-controlled content to arbitrary paths and execute arbitrary OS…
When was CVE-2026-73697 made public?
CVE-2026-73697 was made public on November 2, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 2, 2026. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-73697 actively exploited?
CVE-2026-73697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73697?
CVE-2026-73697 has a CVSS base score of 8.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending). EchelonGraph synthesises the CNA's CVSS + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2026-73697?
A fix for CVE-2026-73697 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-73697 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73697
Is Your Infrastructure Affected by CVE-2026-73697?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.