CVE-2020-15612
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 · uneditedThis 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_ftp_manager.php. When parsing the userLogin 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-9737.
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 confidenceA command injection vulnerability exists in CentOS Web Panel's ajax_ftp_manager.php where the userLogin parameter is not validated before being passed to a system call. An unauthenticated remote attacker can execute arbitrary code as root by injecting shell commands through this parameter.
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= 0.9.8.923CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify CentOS Web Panel is installedCheck for the presence of CWP by looking for /usr/local/cwpsrv/ or the admin panel login page at port 2030 or 2086Affected if CWP is not installed on the system
-
Confirm the CWP versionCheck the version file typically located at /usr/local/cwpsrv/version or access the admin panel and look for version information in the footer or about sectionAffected if The installed version matches 0.9.8.923 exactly
-
Locate the vulnerable ajax_ftp_manager.php fileCheck for the file at /usr/local/cwpsrv/htdocs/ajax_ftp_manager.php or search for it using: find /usr/local/cwpsrv -name 'ajax_ftp_manager.php'Affected if The file exists in the expected location (CWP 0.9.8.923 contains this vulnerable file)
-
Verify the FTP manager module is accessibleCheck if the file is web-accessible by testing a request to the ajax_ftp_manager.php endpoint or verifying it is not removed/restricted in the web server configurationAffected if The ajax_ftp_manager.php is accessible via HTTP/HTTPS without authentication
The system is affected if CentOS Web Panel version 0.9.8.923 is installed and the ajax_ftp_manager.php file is present and accessible, since the unauthenticated userLogin parameter can be exploited for command injection.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedSanitize and validate the userLogin parameter using whitelist approaches or parameterized methods before using it in any system call. Consider implementing role-based access controls and restricting the privileges of web-facing processes.
Latest CWP version (check vendor for version number containing security fix)
- 1. Check the current CentOS Web Panel version by logging into the panel or running: cat /usr/local/cwpsrv/version
- 2. Navigate to the CWP admin panel and check for available updates under the 'Updates' or 'Settings' section
- 3. If an update is available, apply it through the panel's built-in update mechanism
- 4. Alternatively, download the latest CWP version from the official repository: wget http://centos-webpanel.com/cwp-latest
- 5. Run the update script: sh cwp-latest
- 6. After update, verify the new version does not include the vulnerable ajax_ftp_manager.php or has the command injection patched
- 7. If no update is available from vendor, consider restricting access to the ajax_ftp_manager.php file via web server configuration (e.g., .htaccess or nginx location blocks) to block external access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15612 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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