CVE-2016-10792
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 59.9999.145 allows code execution in the context of other accounts via mailman list archives (SEC-141).
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 59.9999.145 contains a vulnerability in its mailman integration that allows an attacker to execute code in the context of other cPanel accounts through mailman list archives, potentially enabling cross-account privilege escalation.
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>= 11.51.9999.98, < 11.52.6.6>= 11.54.0.0, < 11.54.0.29>= 55.9999.61, < 56.0.34>= 57.9999.48, < 58.0.29>= 59.9999.58, < 59.9999.145CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Identify cPanel versionRun 'cat /usr/local/cpanel/version' or check the cPanel WHM interface at Home >> Server Information >> cPanel versionAffected if The installed version falls within any of these ranges: 11.51.9999.98 to 11.52.6.5, 11.54.0.0 to 11.54.0.28, 55.9999.61 to 56.0.33, 57.9999.48 to 58.0.28, or 59.9999.58 to 59.9999.144
-
Verify mailman is installed and enabledCheck if the mailman service exists on the server: run 'ls -la /usr/local/cpanel/3rdparty/mailman/' or check via WHM at Home >> Plugins >> Mailman ListsAffected if Mailman is installed and the cPanel version is in an affected range (see step 1)
-
Identify active mailman mailing listsRun '/usr/local/cpanel/3rdparty/mailman/bin/list_lists' to enumerate existing mailing lists, or check /var/lib/mailman/lists/ for list directoriesAffected if Any mailman lists exist on the server AND the cPanel version is in an affected range (see step 1)
-
Check mailman archive configurationInspect mailman archive settings at /var/lib/mailman/archives/ or via '/usr/local/cpanel/3rdparty/mailman/bin/config_list -l <listname>' to see if public archives are enabledAffected if Public archiving is enabled for any mailman list AND the cPanel version is in an affected range (see step 1)
Your environment is affected if the cPanel version matches any of the five affected ranges AND mailman with accessible list archives is configured 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 data11.52.6.611.54.0.2956.0.34
Upgrade cPanel to version 59.9999.145 or later to patch the vulnerability. Prior to upgrade, restrict mailman administrative access and monitor for suspicious mailman archive activity.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10792 — 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-2016-10792 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