CVE-2017-18470
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 · uneditedcPanel before 62.0.4 has a fixed password for the Munin MySQL test account (SEC-196).
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 confidencecPanel versions before 62.0.4 contain a hardcoded/fixed password for the Munin MySQL test account. This hardcoded credential allows unauthorized attackers to potentially access the MySQL database used by Munin monitoring, leading to confidentiality and integrity compromise.
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>= 11.54.0.0, < 11.54.0.36>= 55.9999.61, < 56.0.43>= 57.9999.48, < 58.0.43>= 59.9999.58, < 60.0.35>= 61.9999.55, < 62.0.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check cPanel versionRun the command to display the cPanel version (e.g., via WHM interface or command line version check) and compare it to the affected ranges: 11.54.0.0 to 11.54.0.35, 55.9999.61 to 56.0.42, 57.9999.48 to 58.0.42, 59.9999.58 to 60.0.34, or 61.9999.55 to 62.0.3Affected if The installed version falls within any of these ranges and is earlier than 62.0.4
-
Verify Munin MySQL test account existsQuery MySQL for user accounts related to Munin monitoring (look for test accounts or monitoring-specific users in the mysql.user table)Affected if A dedicated Munin MySQL test account is present in the MySQL database
-
Inspect Munin configuration for hardcoded credentialsExamine Munin configuration files for stored MySQL credentials, focusing on any test account configurationsAffected if A fixed or static password is found hardcoded in the Munin MySQL configuration rather than a unique, randomly generated credential
-
Review MySQL access logs for the Munin test accountCheck MySQL error logs and general logs for authentication attempts or successful connections from the Munin test account, particularly from unexpected IP addressesAffected if Unauthorized or unexpected authentication attempts from the Munin MySQL test account are found in the logs
The system is affected if it runs a cPanel version earlier than 62.0.4 within the specified ranges AND has the Munin MySQL test account configured with the hardcoded credential.
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.
From vendor data11.54.0.3656.0.4358.0.43
Upgrade cPanel to version 62.0.4 or later to obtain the patched version. If the system has already been deployed, change the Munin MySQL test account password to a strong, unique credential and verify no unauthorized access has occurred.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18470 — 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-2017-18470 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