Skip to main content
VulnerabilityPublished Updated

CVE-2026-29201: WebPros cPanel · Relative Path Traversal

Affects WebPros cPanelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High · fixed in 11.136.0.9 : patch WebPros cPanel soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.136.0.9, 11.134.0.25, 11.132.0.31 +10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
WebProscPanelAffected
  • >=11.136.0.0 <11.136.0.9
Fixed in
  • 11.136.0.9
WebProscPanelAffected
  • >=11.134.0.0 <11.134.0.25
Fixed in
  • 11.134.0.25
WebProscPanelAffected
  • >=11.132.0.0 <11.132.0.31
Fixed in
  • 11.132.0.31
WebProscPanelAffected
  • >=11.130.0.0 <11.130.0.22
Fixed in
  • 11.130.0.22
WebProscPanelAffected
  • >=11.126.0.0 <11.126.0.58
Fixed in
  • 11.126.0.58
WebProscPanelAffected
  • >=11.124.0.0 <11.124.0.37
Fixed in
  • 11.124.0.37

AI-suggested

If you cannot patch yet, restricting access to the adminbin interface and limiting exposure of vulnerable cPanel versions may reduce risk.

Description

Insufficient input validation of the feature file name in `feature::LOADFEATUREFILE` adminbin call can cause arbitrary file read when a relative file path is passed.

References

Community reviews

Loading reviews…