dbcve.org
CpanelApplication

CVE-2016-10806

MEDIUM · 5.4 CVSS v3.0 Published 2019-08-07
Fix available
A fix is available. Upgrade to 11.54.0.24 / 56.0.15 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
cPanel before 57.9999.54 allows self XSS on the Paper Lantern Landing Page (SEC-110).

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 confidence

cPanel before version 57.9999.54 contains a self Cross-Site Scripting (XSS) vulnerability in the Paper Lantern theme landing page. An attacker can inject malicious JavaScript that executes in the victim's own browser when they view a crafted payload on the affected page.

MitigationUpgrade cPanel to version 57.9999.54 or later to patch the XSS vulnerability in the Paper Lantern Landing Page.

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
CpanelApplication
Affected:>= 11.54.0.0, < 11.54.0.24>= 55.9999.61, < 56.0.15>= 57.9999.48, < 57.9999.54

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed cPanel version
    Run: /usr/local/cpanel/cpanel -V or grep version from /usr/local/cpanel/version
    Affected if The version falls within any of these ranges: 11.54.0.0 to 11.54.0.23, 55.9999.61 to 56.0.14, or 57.9999.48 to 57.9999.53
  2. Verify Paper Lantern theme is active
    Check /var/cpanel/users/[username] for 'theme=paper_lantern' or check via WHM interface at: Home >> Themes >> Paper Lantern
    Affected if Paper Lantern theme is currently selected as the active theme for the account
  3. Confirm landing page is accessible
    Access the cPanel login page at /frontend/paper_lantern/index.html or the domain root with cPanel loaded
    Affected if The Paper Lantern themed login or landing page loads without error

You are affected if your cPanel version matches one of the three affected version ranges AND the Paper Lantern theme is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 11.54.0.24 / 56.0.15 / 57.9999.54 or later
Fixed in 11.54.0.2456.0.1557.9999.54
Interim mitigation

Upgrade cPanel to version 57.9999.54 or later to patch the XSS vulnerability in the Paper Lantern Landing Page.

Fix this in Cpanel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10806 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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