CVE-2020-26106
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 88.0.3 has weak permissions (world readable) for the proxy subdomains log file (SEC-558).
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 88.0.3 stores proxy subdomain log files with world-readable permissions (chmod 644 or similar), allowing any local user on the system to read potentially sensitive log data including request details, session tokens, and other information that may be logged from proxy subdomain traffic.
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< 88.0.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Determine cPanel versionRun '/usr/local/cpanel/cpanel -V' or check via WHM API using 'whmapi1 get_cpanel_version' to retrieve the installed cPanel versionAffected if The installed version is below 88.0.3 (e.g., 88.0.2, 88.0.1, 87.x, or earlier)
-
Locate proxy subdomain log filesIdentify log files associated with proxy subdomains in the cPanel log directory structure (typically under /var/log/ or within the user's domain directory)Affected if Proxy subdomain log files exist on the system
-
Check log file permissionsUse 'ls -la' on the identified proxy subdomain log files to view their permission bitsAffected if The log files have permissions set to 644 (rw-r--r--) or otherwise readable by others (e.g., world-readable group or other permissions)
-
Verify world-readable statusConfirm that permissions allow access by non-owner users by testing with a non-privileged account or checking permission bits for 'other' read accessAffected if Users other than the file owner can read the proxy subdomain log files
You are affected if your cPanel version is below 88.0.3 AND proxy subdomain log files exist with permissions that allow read access by non-owner users (chmod 644 or similar world-readable settings).
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 data88.0.3
Update cPanel to version 88.0.3 or later, which contains the fix for SEC-558. Alternatively, manually restrict permissions on the affected log files to owner-only read access (chmod 600) as an immediate workaround.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26106 — 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-2020-26106 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