Control Web Panel (CWP) < 1.16 SQL Injection via access_token() API
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.16
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Control Web Panel (CWP) versions before 1.16 (webpanel_version)
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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? →
- 14/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? →
- Specific setups only
- Fix
- Fixed in 1.16
- 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), a web hosting control panel, is affected by a SQL injection flaw in its internal API authentication check. Attackers can exploit this to read arbitrary database contents and bypass the API's authentication, potentially gaining unauthorized control over the server.
Read the original description
Control Web Panel (CWP) before webpanel_version 1.16 contains a SQL injection vulnerability in the loopback API authentication gate access_token(), which connects to MySQL as root and interpolates attacker-controlled values directly into its query. Attackers can inject SQL through the authorization_code and client_id parameters to read arbitrary database contents and forge the authentication result, bypassing the API's authentication check.
What to do
Check whether your setup matches what the bug needs.
Control Web Panel (CWP) versions before 1.16 (webpanel_version)Upgrade to a fixed version: 1.16.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Control Web Panel Control Web Panel
fixed in 1.16
Evidence 3
- Patch
- Exploit
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-77879
What does this mean?
A SQL injection flaw in the access_token() API of Control Web Panel lets an attacker send crafted input that is run as database queries. This can read arbitrary database contents and forge the authentication result, bypassing the API's authentication check.Source: vulncheck.com
Am I affected, and how do I check?
Control Web Panel (CWP) versions before 1.16 are affected, as shown by the webpanel_version value. To check a installation, look up the webpanel_version reported by the panel.Source: vulncheck.com
What should I do about it?
Upgrade Control Web Panel to version 1.16 or later, which is the listed fixed version.Source: vulncheck.com
Is it 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