dbcve.org
WebpanelApplication · Control Webpanel

CVE-2020-15610

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 execute arbitrary code 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_php_pecl.php. When parsing the modulo parameter, the process does not properly validate a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-9728.

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 command injection vulnerability in CentOS Web Panel's ajax_php_pecl.php. The modulo parameter is not validated before being passed to a system call, allowing remote attackers to execute arbitrary commands as root.

MitigationRestrict network access to the affected CWP management interface and apply vendor patch when available; until patched, consider disabling or firewalling the ajax_php_pecl.php endpoint.

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
High
Availability
High

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

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 CentOS Web Panel installation
    Check for CWP by looking for its installation directories (commonly /usr/local/cwpsrv, /usr/local/cwp) or by running: rpm -qa | grep -i centos-web-panel or ls -la /usr/local/cwp* 2>/dev/null
    Affected if CWP is installed on the system
  2. Check CWP version
    Run: cat /usr/local/cwpsrv/VERSION or cat /usr/local/cwp/version or check the admin interface version info. Compare against affected version 0.9.8.923
    Affected if The installed version matches 0.9.8.923
  3. Locate vulnerable ajax_php_pecl.php file
    Find the file by running: find /usr/local/cwp -name 'ajax_php_pecl.php' 2>/dev/null
    Affected if The file exists at the expected path within the CWP installation directory
  4. Verify network exposure of the vulnerable endpoint
    Check if the CWP admin interface (port 2031 or 2086) is exposed to untrusted networks. Run: curl -s http://localhost:2031/ajax_php_pecl.php -o /dev/null -w '%{http_code}' to confirm the endpoint is accessible locally, then verify firewall rules for external access
    Affected if The ajax_php_pecl.php endpoint is reachable from untrusted network addresses (not restricted to localhost or trusted IPs)
  5. Inspect the modulo parameter handling in the vulnerable file
    Examine the source code of ajax_php_pecl.php and look for the modulo parameter usage: grep -n 'modulo' /path/to/ajax_php_pecl.php. Check if the modulo value is used directly in shell_exec, exec, system, or passthru calls without proper sanitization
    Affected if The modulo parameter from $_GET or $_POST is passed directly to a PHP execution function without input validation

You are affected if CWP version 0.9.8.923 is installed and the ajax_php_pecl.php file is accessible, as the unvalidated modulo parameter can allow unauthenticated remote command execution.

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

Restrict network access to the affected CWP management interface and apply vendor patch when available; until patched, consider disabling or firewalling the ajax_php_pecl.php endpoint.

Fix this in Webpanel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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