CVE-2018-20917
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 70.0.23 allows any user to disable Solr (SEC-371).
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 70.0.23 contains an authorization flaw where any authenticated user can disable the Apache Solr search service, regardless of their privilege level. This is a privilege escalation/authorization vulnerability in the cPanel management interface.
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< 70.0.23CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 if cPanel is installedVerify cPanel is present on the system by checking for the cPanel directory structure at /usr/local/cpanel or by running: ls -la /usr/local/cpanelAffected if cPanel must be installed for this vulnerability to apply
-
Determine installed cPanel versionRun the command: cat /usr/local/cpanel/version or rpm -q cpanel or use the cPanel API: whmapi1 versionAffected if Unable to determine the cPanel version for comparison
-
Compare version against affected rangeParse the version output and compare it numerically to 70.0.23. Versions are compared as (major * 10000) + (minor * 100) + patch. For example, 70.0.22 = 7000022 and 70.0.23 = 7000023Affected if The installed version is less than 70.0.23 (e.g., 70.0.22, 68.x.x, etc.)
-
Verify Apache Solr service status (optional context)If cPanel is vulnerable, check if Apache Solr is enabled by examining: /var/cpanel/service Solr or querying WHM API: whmapi1 service status service=solrAffected if Apache Solr is enabled and could be disabled by any privileged user
The environment is affected if cPanel is installed and the installed version is numerically less than 70.0.23, allowing any authenticated user to disable the Apache Solr service regardless of their privilege level.
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 data70.0.23
Upgrade cPanel to version 70.0.23 or later to patch the authorization bypass. Verify Solr functionality after the upgrade.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20917 — 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-2018-20917 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