CVE-2017-18411
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 · uneditedThe "addon domain conversion" feature in cPanel before 67.9999.103 can copy all MySQL databases to the new account (SEC-285).
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 · moderate confidenceThe 'addon domain conversion' feature in cPanel before version 67.9999.103 contains a vulnerability that allows copying all MySQL databases to the new account during the conversion process (SEC-285). This represents an authorization flaw where database access is improperly granted during domain conversion, potentially leading to unauthorized data exposure or 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>= 55.9999.61, < 56.0.52>= 59.9999.58, < 60.0.48>= 61.9999.55, < 62.0.30>= 64.0.0, < 64.0.40>= 65.9999.38, < 66.0.23>= 67.9999.64, < 67.9999.103CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check cPanel version via command lineRun the command: /usr/local/cpanel/cpanel -V or cat /usr/local/cpanel/versionAffected if The installed version falls within any of these ranges: 55.9999.61 to 56.0.51, 59.9999.58 to 60.0.47, 61.9999.55 to 62.0.29, 64.0.0 to 64.0.39, 65.9999.38 to 66.0.22, or 67.9999.64 to 67.9999.102
-
Check cPanel version via WHM interfaceLog into WHM and navigate to Server Information or run: whmapi1 get_cpanel_versionAffected if The version displayed matches any of the affected ranges listed above
-
Review addon domain conversion logsCheck cPanel logs for addon domain conversion operations: grep -r 'addon domain' /var/log/cpanel* or look in /var/cpanel/logs/ for conversion-related entriesAffected if Conversion operations exist and the cPanel version is in the affected list
-
Audit recent domain conversions in cPanelCheck /var/cpanel/users/ directories for accounts that may have been created via domain conversion, or review the transfer log at /var/log/cpanel/transfers.logAffected if Domain conversions have occurred and the server runs an affected cPanel version
You are affected if your cPanel version falls within any of the vulnerable version ranges AND addon domain conversion has been performed on the server.
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 data56.0.5260.0.4862.0.30
Update cPanel to version 67.9999.103 or later to patch this vulnerability. This is a vendor-supplied patch addressing the SEC-285 issue.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18411 — 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-18411 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