dbcve.org
WebpanelApplication · Control Webpanel

CVE-2020-15618

HIGH · 7.5 CVSS v3.1 Published 2020-07-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability allows remote attackers to disclose sensitive information on affected installations of CentOS Web Panel cwp-e17.0.9.8.923. Authentication is not required to exploit this vulnerability. The specific flaw exists within ajax_list_accounts.php. When parsing the username parameter, the process does not properly validate a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to disclose information in the context of root. Was ZDI-CAN-9717.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated SQL injection in CentOS Web Panel's ajax_list_accounts.php. The username parameter is not properly validated before being used in SQL query construction, allowing remote attackers to inject malicious SQL queries and disclose sensitive information in the root context without any authentication.

MitigationReplace dynamic SQL query construction with parameterized queries/prepared statements in ajax_list_accounts.php, and implement proper input validation for all user-supplied parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebpanelApplication
Affected:= 0.9.8.923

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm CentOS Web Panel installation
    Check if the file /usr/local/cwpsrv/htdocs exists, or look for the CWP admin interface at port 2086 or 2087
    Affected if The system has CentOS Web Panel installed
  2. Identify the CWP version
    Check the version file typically at /usr/local/cwpsrv/version or access the admin login page which often displays the version
    Affected if The installed version matches 0.9.8.923 exactly
  3. Locate the vulnerable script
    Check if the file /usr/local/cwpsrv/htdocs/ajax/ajax_list_accounts.php exists on the system
    Affected if The file ajax_list_accounts.php is present in the expected location
  4. Verify vulnerable code pattern
    Inspect ajax_list_accounts.php and search for direct use of $_GET['username'] or $_POST['username'] in SQL queries without sanitization or prepared statements
    Affected if The username parameter is used directly in SQL queries without parameterized queries or input validation
  5. Test unauthenticated access to endpoint
    Send a request to ajax_list_accounts.php with a SQL injection payload in the username parameter, for example: curl 'http://localhost:2086/ajax/ajax_list_accounts.php?username=' -d 'value=1'
    Affected if The endpoint responds without requiring authentication and reflects SQL injection behavior
  6. Check for recent compromise indicators
    Review web server access logs for unusual queries to ajax_list_accounts.php containing SQL syntax characters like quotes, UNION, or SELECT
    Affected if Suspicious SQL injection patterns appear in access logs targeting this endpoint

The system is affected if CentOS Web Panel version 0.9.8.923 is installed and the ajax_list_accounts.php file exists with the vulnerable username parameter handling accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL query construction with parameterized queries/prepared statements in ajax_list_accounts.php, and implement proper input validation for all user-supplied parameters.

Fix this in Webpanel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15618 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15618 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data