CPanel and WHM Authentication Bypass – CVE-2026-41940
51–60 of 64 posts
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#52Earlier quoted context omitted.
Yeah, I hate all those terrible regulations that keep people from burning alive in their homes too. Godddamn goverment saving lives, it's so slightly annoying. Wait. Wasn't there a whole group of people who thought this way recently? Wasn't it called the Department of Government Efficiency? Wasn't it led by a rich tech bro who wants to live on Mars? Didn't they get disbanded because it was a bunch of armchair experts…
What regulations would you suggest would be the software equivalent of a fire code? What kind of penalties would apply for not meeting these regulations? Who would be responsible for enforcement? Do you propose this should apply internationally? Or just to software written in a specific region? Or is the location of where software is hosted (or the headquarters of the company operating the hardware) a better target f…
Hmm, I wonder how the FDA approves software in a medical devices context. Or if the EU AI act is in any way a precedent.
Oh well, we'll never know.
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#53Low key wonder if people using LLMs to scan these old code bases for corner case issues and fining treasure troves of exploits.
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#54Everytime I read one of these it always boils down to the same thing..Don't solve solved problems. And the best code in this case is code you didn't write as PHP's session handler is battle-tested but every line you write to roll your own is a line you have to secure, maintain, and eventually patch at 2am when someone finds the bug. Session handling, auth, crypto, password hashing etc - all these are the exact areas…
Sometimes it makes sense to roll your own and the cost of a dependency isn't worth it. This can be especially true when you need to accommodate many bespoke environments and you end up needing to make little accomodations here and there. Can create a very unpleasant situation when you don't own the code.
I'm not a cryptographer but I've spent a significant portion of my career focusing on the security-side of things and I've rolled my own auth quite a few times on very public projects you can access today and I've never had any significant findings through repeated pentests.
But that's just the thing: I did it the right way, and there is a right way to roll your own stuff, to forge it in a way it comes out suitable. Is it bug free? Probably not, but I feel significantly better about it having thoroughly tested it by myself, my colleagues and paid professional penetration testers.
I couldn't easily find an answer but I'd like to know if this implementation has been validated by a professional or not.
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#55I would think that for everyone that needs some help, there must be 10 who self served…
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#56Y'know what would help protect those internet buildings from falling on people? A software building code
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#57They should have switched to a web framework long ago
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#58What a shame that I no longer have access to my teenage-level conscience, I am sallivating at the idea of going wild with this and the Copy Fail cve. The potential here to do all kinds of manipulation for search engines / AI tools is enormous. Perhaps the more scary thought is that someone could easily make an agent that would exploit both bugs to wipe out servers. Good on these companies to publish their findings st…
Re: CPanel and WHM Authentication Bypass – CVE-2026-41940
#59cPanel being the backbone of the internet's cheap hosting layer was already a monoculture risk waiting to bite us - turns out we didn't have to wait long