dbcve.org
WebpanelApplication · Control Webpanel

CVE-2020-15619

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 type 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-9723.

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

This is an unauthenticated SQL injection vulnerability in CentOS Web Panel's ajax_list_accounts.php. The 'type' parameter is not properly validated before being used in SQL query construction, allowing remote attackers to inject malicious SQL commands and extract sensitive database information.

MitigationApply the vendor patch immediately. Until then, disable or restrict access to ajax_list_accounts.php. Implement proper input validation and use parameterized queries/prepared statements for all database operations.

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 is installed
    Identify the web panel software running on the server. Look for CWP (CentOS Web Panel) in the web interface or check for its characteristic file paths and service processes.
    Affected if The server is running CentOS Web Panel.
  2. Check installed CWP version
    Locate the version file or check the admin interface for the exact installed version number. Compare against 0.9.8.923.
    Affected if The installed version is 0.9.8.923.
  3. Verify ajax_list_accounts.php exists
    Check for the presence of the file ajax_list_accounts.php in the CWP web directory, typically found in /usr/local/cwpsrv/htdocs/ or the document root.
    Affected if The file ajax_list_accounts.php exists on the server.
  4. Determine if ajax_list_accounts.php is externally accessible
    Test network access to the ajax_list_accounts.php endpoint from an untrusted network. Look for responses at paths like /ajax_list_accounts.php or /cwp/ajax_list_accounts.php.
    Affected if The endpoint is reachable from outside trusted networks without authentication.
  5. Test for SQL injection via type parameter
    Send an HTTP request to ajax_list_accounts.php with a crafted 'type' parameter containing SQL injection payloads (e.g., type=1' OR '1'='1). Observe if the application returns unexpected database errors or differs in behavior from normal requests.
    Affected if The application responds to SQL injection payloads in the type parameter without proper sanitization.

The server is affected if it runs CentOS Web Panel version 0.9.8.923 with the ajax_list_accounts.php endpoint exposed and vulnerable to SQL injection via the type parameter.

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

Apply the vendor patch immediately. Until then, disable or restrict access to ajax_list_accounts.php. Implement proper input validation and use parameterized queries/prepared statements for all database operations.

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-15619 — 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-15619 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