dbcve.org
WebpanelApplication · Control Webpanel

CVE-2020-15617

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 status 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-9708.

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

SQL injection vulnerability in CentOS Web Panel's ajax_list_accounts.php allows unauthenticated remote attackers to inject malicious SQL queries via the 'status' parameter. Since the application runs with root database privileges, attackers can potentially exfiltrate sensitive system data. The vulnerability stems from insufficient input validation before constructing SQL statements.

MitigationImplement proper input validation and use parameterized queries (prepared statements) for all database operations. Additionally, run the database connection with minimal required privileges rather than root-level access.

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. Identify the installed software product
    Check if CentOS Web Panel (CWP) is installed on the system by looking for /usr/local/cwpsrv/ or running 'rpm -qa | grep -i centos-webpanel'
    Affected if The system does not have CentOS Web Panel installed, then this CVE does not apply
  2. Determine the exact CWP version
    Check the CWP version file, typically located at /usr/local/cwpsrv/version or use the command 'cat /usr/local/cwpsrv/version'
    Affected if The installed version is exactly 0.9.8.923 (the only version listed as affected)
  3. Locate the vulnerable script
    Verify that ajax_list_accounts.php exists in the web directory, commonly found at /usr/local/cwpsrv/htdocs/ajax_list_accounts.php
    Affected if The file exists and is accessible via the web server
  4. Verify the status parameter is processed
    Examine the ajax_list_accounts.php file and look for code that uses the 'status' parameter in SQL queries without proper sanitization
    Affected if The script processes the 'status' parameter directly in SQL queries without parameterized queries or input validation
  5. Confirm database connection privileges
    Check the database configuration file (usually /usr/local/cwpsrv/htdocs/resources/admin/include/db_connect.php or similar) to see the database user privileges
    Affected if The CWP database connection uses root-level privileges rather than a limited database user

A system is affected if it runs CentOS Web Panel version 0.9.8.923 with the ajax_list_accounts.php script accessible and using the 'status' parameter in SQL queries without proper input validation.

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

Implement proper input validation and use parameterized queries (prepared statements) for all database operations. Additionally, run the database connection with minimal required privileges rather than root-level access.

Fix this in Webpanel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15617 — 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-15617 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