CVE-2017-18414
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 67.9999.103 allows an open redirect in /unprotected/redirect.html (SEC-300).
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 before version 67.9999.103 contains an open redirect vulnerability in the /unprotected/redirect.html endpoint. This allows attackers to craft malicious URLs appearing to originate from the legitimate cPanel domain, potentially facilitating phishing attacks by redirecting users to attacker-controlled websites.
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< 56.0.52>= 57.9999.48, < 60.0.48>= 61.9999.55, < 62.0.30>= 62.0.31, < 64.0.40>= 64.0.42, < 66.0.23>= 66.0.24, < 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/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.
-
Confirm cPanel is installedCheck for cPanel by looking for /usr/local/cpanel or running: which cpanel; ls -la /usr/local/cpanel 2>/dev/nullAffected if cPanel is not present in the environment, the vulnerability does not apply
-
Identify the installed cPanel versionRun: /usr/local/cpanel/cpanel -V or cat /usr/local/cpanel/version 2>/dev/nullAffected if The version displayed falls within any of these ranges: < 56.0.52; >= 57.9999.48 and < 60.0.48; >= 61.9999.55 and < 62.0.30; >= 62.0.31 and < 64.0.40; >= 64.0.42 and < 66.0.23; >= 66.0.24 and < 67.9999.103
-
Verify the vulnerable endpoint existsCheck if /usr/local/cpanel/base/frontend/paper_lantern/unprotected/redirect.html or /usr/local/cpanel/base/unprotected/redirect.html exists on the serverAffected if The file exists and the cPanel version is in the affected ranges above
A user is affected if they are running any cPanel version before 67.9999.103 that falls within the specified version ranges and the /unprotected/redirect.html endpoint is present and accessible.
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 the open redirect vulnerability in /unprotected/redirect.html.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18414 — 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-18414 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