# CVE-2026-41940: WebPros cPanel & WHM and WP2 (WordPress Squared) Missing Authentication for Critical Function

> Unauthenticated remote attackers can bypass login controls to gain unauthorized access to the cPanel and WHM control panel.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 30 Apr 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-85qr-8rxc-62gv

## What is CVE-2026-41940?

CVE-2026-41940 is a critical authentication bypass vulnerability in Cpanel Cpanel, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cPanel and WHM versions after 11.40 contain an authentication bypass vulnerability in the login flow that allows unauthenticated remote attackers to gain unauthorized access to the control panel.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-41940?

It affects 3 products.


Products: Cpanel Cpanel, Cpanel Whm, Cpanel Wp Squared.

## How do I fix CVE-2026-41940?

No fix has been published for CVE-2026-41940 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2026.

## Is CVE-2026-41940 being exploited?

Yes. Attackers have exploited CVE-2026-41940 in the wild since at least 30 Apr 2026, including in ransomware campaigns.

Public exploit code:

- CVE-2026-41940 — cPanel & WHM Authentication Bypass via Session-File CRLF Injection (github_poc): https://github.com/ynsmroztas/cPanelSniper
- High fidelity scanner for CVE-2026-41940 (cPanel & WHM authentication bypass) (github_poc): https://github.com/assetnote/cpanel2shell-scanner
- https://github.com/XsanFlip/poc-cpanel-cve-2026-41940 (github_poc): https://github.com/XsanFlip/poc-cpanel-cve-2026-41940
- https://github.com/adriyansyah-mf/cve-2026-41940-poc (github_poc): https://github.com/adriyansyah-mf/cve-2026-41940-poc
- https://github.com/ZeroDayEvil/CVE-2026-41940-PoC (github_poc): https://github.com/ZeroDayEvil/CVE-2026-41940-PoC
- CVE-2026-41940 latest cPanel & WHM 0day - 70 million websites are possible to expose by Chirag Artani (github_poc): https://github.com/Sachinart/CVE-2026-41940-cpanel-0day

## Other vulnerabilities in Cpanel Cpanel

- [CVE-2003-1425](https://insights.sbomify.com/CVE-2003-1425/): guestbook.cgi in cPanel 5.0 allows remote attackers to execute arbitrary commands via the template parameter. (critical 10.0)
- [CVE-2004-1769](https://insights.sbomify.com/CVE-2004-1769/): Code injection in n/a (critical 10.0)
- [CVE-2004-1770](https://insights.sbomify.com/CVE-2004-1770/): Command injection in n/a (critical 10.0)
- [CVE-2020-26098](https://insights.sbomify.com/CVE-2020-26098/): Command injection in n/a (critical 9.8)
- [CVE-2020-26100](https://insights.sbomify.com/CVE-2020-26100/): Privilege escalation in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41940 and fix it if it is affected.

What it is: CVE-2026-41940 is a critical authentication bypass vulnerability in Cpanel Cpanel, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-41940 in the wild since at least 30 Apr 2026, including in ransomware campaigns.

Affected product: Cpanel Cpanel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41940/ (Markdown: https://insights.sbomify.com/CVE-2026-41940/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41940
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41940
- OSV: https://osv.dev/vulnerability/CVE-2026-41940

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41940/
Summaries are generated and may contain mistakes; the official description above is the record.