Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Critical Vulnerability with cPanel & WHM Login Authentication

2

Comments

  • HxxxHxxx Member

    @catding said:
    Too late. My cPanel was hacked yesterday already. That's a sad story.

    What happened? if your server was auto patching daily which i think is normal it should have downloaded the patch.

  • avsispavsisp Member, Patron Provider

    @CristianD said:
    So the problem has existed since February 23 and was reported to cPanel, but they didn’t take any action.

    Who is going to pay for this? Data loss, compromised servers, companies having to reinstall systems, all the work involved, the downtime, etc. In my opinion, cPanel should be held responsible for this. Yes, I know you’ll say companies should have backups — and that’s true — but what about the time, effort, and downtime required to rebuild servers and websites?

    If I make a mistake, I am held accountable and I pay for it. Why should it be different here?

    How come nobody is talking about this on the cPanel Community? I haven’t found any discussions about it. Is this being ignored or hidden?

    Will anybody sue cPanel? I’m curious about this — someone should.

    Move to DirectAdmin - problem solved.

    Thanked by 1suyadi92
  • EthernetServersEthernetServers Member, Patron Provider

    Detection Script
    Due to the complexity of the traces found, we have had to make several iterations of this script in order to remove false positive results. We are currently working on an updated version, and it will be added here once available.

    https://support.cpanel.net/hc/en-us/articles/40073787579671-Security-CVE-2026-41940-cPanel-WHM-WP2-Security-Update-04-28-2026

  • ascicodeascicode Member

    @avsisp said:

    @CristianD said:
    So the problem has existed since February 23 and was reported to cPanel, but they didn’t take any action.

    Who is going to pay for this? Data loss, compromised servers, companies having to reinstall systems, all the work involved, the downtime, etc. In my opinion, cPanel should be held responsible for this. Yes, I know you’ll say companies should have backups — and that’s true — but what about the time, effort, and downtime required to rebuild servers and websites?

    If I make a mistake, I am held accountable and I pay for it. Why should it be different here?

    How come nobody is talking about this on the cPanel Community? I haven’t found any discussions about it. Is this being ignored or hidden?

    Will anybody sue cPanel? I’m curious about this — someone should.

    Move to DirectAdmin - problem solved.

    Don't think that long until something happens there.

    Thanked by 1ariq01
  • slowserversslowservers Member, Host Rep

    This seems unrelated, but I just banned a SporeStack token for trying to hack into someone's cPanel yesterday.

    These were the logs:

    [2026-04-30 14:17:41 -0400] info [whostmgrd] (IP) - root "POST /login/?login_only=1 HTTP/1.1" FAILED LOGIN whostmgrd: user password incorrect
    [2026-04-30 14:17:41 -0400] info [whostmgrd] (IP) - root "POST /login/?login_only=1 HTTP/1.1" FAILED LOGIN whostmgrd: user password incorrect
    [2026-04-30 14:17:41 -0400] info [whostmgrd] (IP) - root "POST /login/?login_only=1 HTTP/1.1" FAILED LOGIN whostmgrd: user password incorrect
    [2026-04-30 14:17:41 -0400] info [whostmgrd] (IP) - root "POST /login/?login_only=1 HTTP/1.1" FAILED LOGIN whostmgrd: user password incorrect
    [2026-04-30 14:17:43 -0400] info [whostmgrd] (IP) - root "GET /cpsess4012667622/json-api/version HTTP/1.1" FAILED LOGIN whostmgrd: user password incorrect
    
    
    Thanked by 1ariq01
  • catdingcatding Member

    We are using a shared hosting. Some websites hosted with them, their cPanel got hacked and we didn't make any backup yet.

    @Hxxx said:

    @catding said:
    Too late. My cPanel was hacked yesterday already. That's a sad story.

    What happened? if your server was auto patching daily which i think is normal it should have downloaded the patch.

  • CristianDCristianD Member, Host Rep

    Can someone please confirm whether the bypass check server uses Python?
    We are using ModSecurity to block any Python requests to our servers, and in our logs there are far too many blocked requests since this issue appeared.
    From what I can see, our servers are completely fine. The servers where we did not have this ModSecurity rule in place were compromised. Once we added the rule, no further issues occurred.

  • JasonMJasonM Member

    cPanel collects (loots) so much money from their users and end-users but it seems to they fail to invest it in security. Now they've got one more reason to increase the price by minimum 15% in 2027

  • MikeAMikeA Member, Patron Provider

    @CristianD said: We are using ModSecurity to block any Python requests to our servers, and in our logs there are far too many blocked requests since this issue appeared.

    How? If you're checking useragents or something that's pointless.

    Thanked by 1tentor
  • Before authentication occurs, cpsrvd (the cPanel service daemon) writes a new session file to the disk. The vulnerability allows an attacker to manipulate the whostmgrsession cookie by omitting an expected segment of the cookie value, avoiding the encryption process typically applied to an attacker-provided value. Attackers can inject raw \r\n characters via a malicious basic authorization header, and the system subsequently writes the session file without sanitizing the data. As a result, the attacker can insert arbitrary properties, such as user=root, into their session file. After triggering a reload of the session from the file, the attacker establishes administrator-level access for their token.

    good ol carriage return and line feed strikes again? can't make this shit up if i tried

    i wonder how long this was working before "being reported"

  • DrvDrv Member

    do eu data protection complain, those mfs got cash to hire competent devs to secure their code.
    but ditch this crap, it's still an attack vector on your server

  • CristianDCristianD Member, Host Rep

    cPanel should pay for all this problem because lots of data was exposed , where is GDPR ?

  • hezekiahsharehezekiahshare Member
    edited May 3

    I just want to say
    It happen from August 2025 .
    So we can say it must be hacked the server more than we know.
    Why I know? Because I found it at September 2025 in one of my user.
    Luckily I'm limiting port access for 2086 2087 and ssh port. So I'm patching my user clean up and everything okay.
    I was patching with a root access on every bruteforce in cpanel and auto ban every ip whoever doing wrong password.

  • PacketraOliverPacketraOliver Member, Patron Provider

    @Andreix said:
    So, cPanel switched to claude-coding?! The CVE is damn serious for a human to miss...

    This is not what happened, has nothing to do with "claude coding", this issue has existed in cPanel since way before, as they stated this "does not affect just some it affects all! update". This has been there for all these years, way before AI became a thing.

    We've had to help quite a few customers restore their VM's from backups, and luckily on 28th moment this was disclosed we started first by locking :2087 :2083 until the patch was released and moment it was we updated our fleet.

    Unfortunately the emails we sent out to our clients fell on deaf ears until 30th+ when they all of a sudden wondered why their site is not working, then you open console to give them the bad news "boot not found", and you just know the rest of this..

    @catding said:
    Too late. My cPanel was hacked yesterday already. That's a sad story.

    It's unfortunate, If you were on Shared hosting I would assume they have a backup but if you are like many others, missed those messages (I mean I hope they sent you a urgent email, we sent out one, then a reminder, along with even a reminder for the CVE affecting the linux kernels). However, I do feel bad for you, we've been having to see people devastated from this one, those who do not have backups :neutral:

    My message to everyone still now is this, If you haven't been HACKED and you havent updated, UPDATE NOW, its not a matter of IF, its WHEN. They are actively scanning for :2087 to just apply this exploit to see the world burn.

    Thanked by 1Andreix
  • PacketraOliverPacketraOliver Member, Patron Provider

    @CristianD said:
    So the problem has existed since February 23 and was reported to cPanel, but they didn’t take any action.

    The problem was discovered in February, which was odd apparently Knownhost knew about it or so I read, I won't stake my reputation on it.

    It's a bit lame if they knew this and didn't disclose, but the problem has existed way before February 23rd, You can apply this hack to even the older versions of cPanel, this one has been there for a while.

  • PacketraOliverPacketraOliver Member, Patron Provider

    Yeah we saw this one, couldnt believe we were firing EA4 updates and another upcp! so close to the other one but luckily this one is not as alarming in the sense its not made public.. Its the season of CVE apparently.

  • cnencccnencc Member

    Anyway, I have three servers whose databases and website files have been deleted.

  • VextroVextro Member

    Here we go again? Received 15 minutes ago

  • CristianDCristianD Member, Host Rep

    Easy peasy — install Cursor/Claude on a VPS with cPanel, tell them to dig into the server and look for cPanel vulnerabilities... have fun. Even ChatGPT, after I asked it to search for cPanel vulnerabilities, told me it could help analyze them, but that doing so against systems without permission would be illegal.

    We wanted AI, now we have AI. It’s just a matter of time, and I guarantee it’s going down not the AI because of the AI. have fun.

  • senmoosenmoo Member

    Wow!
    Thanks!

  • SilverCreekSilverCreek Member, Patron Provider, Megathread Squad

    @Vextro said:
    Here we go again? Received 15 minutes ago

    There will also be releases for CloudLinux, WHMCS, ApisCP and Blesta in the coming weeks. :smiley:

  • AdvinAdvin Member, Host Rep
    edited May 8

    @Andreix said:
    So, cPanel switched to claude-coding?! The CVE is damn serious for a human to miss...

    The vulnerability has been present since cPanel 11.40, which was released over a decade ago. It is, however, surprising that it managed to make it this far without being discovered.

  • zedzed Member

    @Advin said: without being discovered announced

    apologies for the modded quote

  • Noah2002Noah2002 Member

    I found malware files in most of my cPanel accounts today. I have removed all infected files and updated cPanel/WHM to the latest version.

    This is a very serious security concern in the history of cPanel/WHM!

  • JohnMiller92JohnMiller92 Member
    edited May 9

    @CristianD said: We wanted AI, now we have AI.

    only ai i asked for was in games and/or bots :(

  • KlingzzKlingzz Member

    This one looks serious. Has anyone here already patched production servers

  • EthernetServersEthernetServers Member, Patron Provider
    edited May 9

    @Klingzz said:
    This one looks serious. Has anyone here already patched production servers

    Given patches have been out for a while, I certainly hope so... otherwise those servers are likely hosed by now.

  • @dustinc said: no patch is available yet

    Does RackNerd have any plans to offer non-cPanel choices in shared hosting (Black Friday or otherwise)?

  • Another one:

    We are writing to let you know that a cPanel & WHM security patch is expected to be released on Wednesday, May 13, 2026 at 1:00pm EST.

    This release addresses multiple vulnerabilities across versions of cPanel & WHM, including fixes for the following vulnerabilities rated up to High severity.

    CVE-2026-29205

    CVE-2026-29206

    CVE-2026-32991

    CVE-2026-32992

    CVE-2026-32993

    All vulnerabilities were either responsibly disclosed by external researchers or identified internally by our security team. At this time, there are no known exploits or proof-of-concept code in the wild. To help protect customers prior to patch availability, technical details about vulnerabilities will be released alongside the patches.

    Patch & Affected Versions

    The patch will be available on May 13 at 1:00pm EST and will be distributed through the standard cPanel automatic update process and through the manual update process. We strongly recommend performing a manual update once the patch is made available.

    Versions Impacted:

    86, 94, 102, 110, 110 CL6, 118, 124, 126, 130, 132, 134, 136, 136 (WP2)

    Prepare Now

    Identify affected servers. Review your servers on the affected versions above.

    Check the update configuration. For servers where automatic updates are disabled or version-pinned, review /etc/cpupdate.conf now so there are no delays when the patch lands.

    Brief your team. If your environment requires a maintenance window, notify the relevant people so they are ready to act.

    Manual update. To update impacted servers before an automatic update is triggered, run /scripts/upcp once the patch is made available.

    Note for CloudLinux 6 users. Before manually updating, set the update tier to the cl6110 branch

    Watch for a follow-up email with exact patched versions and a link to all technical details in the support article.

    The industry is seeing a sustained rise in discovered vulnerabilities, and AI is accelerating the pace at which they are found and exploited. We are responding by strengthening how we identify, validate, and act on security reports. You will hear from us more frequently as our processes evolve. This is intentional. We believe clear, timely communication is part of how we keep you protected.

    We will follow up the moment the patch is live with full details and remediation steps.

    Please reach out to your account manager or our support team, if you have any questions or need further guidance.

    Thank you for your continued partnership.

    Best regards,
    Your cPanel Security Team

This discussion has been closed.