CVE-2017-18460
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.17 allows arbitrary code execution during automatic SSL installation (SEC-221).
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 confidencecPanel before version 62.0.17 contains a vulnerability (SEC-221) that allows arbitrary code execution during the automatic SSL installation process. An attacker with the ability to trigger or intercept the automatic SSL installation workflow can execute arbitrary code with the privileges of the cPanel service.
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>= 59.9999.58, < 60.0.39>= 61.9999.55, < 62.0.17CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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.
-
Determine installed cPanel versionRun /usr/local/cpanel/cpanel -V or access WHM > Server Status > cPanel VersionAffected if Version is below 62.0.17 (vulnerable range: 59.9999.58 to 60.0.39, or 61.9999.55 to 62.0.16)
-
Check if automatic SSL installation is enabledIn WHM, navigate to SSL/TLS > AutoSSL or check /var/cpanel/autossl* configuration files for enabled statusAffected if AutoSSL feature is enabled and accessible to the attacker
-
Verify user access controls for SSL certificate operationsReview cPanel account privileges and reseller permissions in /var/cpanel/users/ or via WHM > Reseller CenterAffected if Low-privilege or reseller accounts can trigger AutoSSL workflows
-
Examine SSL installation logs for unauthorized activityReview /var/log/cpanel/autossl.log and /var/log/cpanel/ssl-log for unexpected certificate installation eventsAffected if Certificate installation events exist that were not initiated by administrators
The environment is affected if cPanel version is below 62.0.17 AND the AutoSSL feature is enabled or accessible to non-administrator accounts.
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 data60.0.3962.0.17
Upgrade cPanel to version 62.0.17 or later to remediate this vulnerability. For systems that cannot immediately upgrade, restrict access to the automatic SSL installation features and monitor for unauthorized certificate operations.
- 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-18460 — 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-18460 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