I have lifted this request out of the webpanel bugs and into the direct topic as it is imperative that attention is directed to the topic from the CWP team
In both version 2.0.10 and 1.30.10, the changelog says:
"ModSecurity is now installed from the CWP repository as a package (cwp-mod_security2) with an up-to-date OWASP Core Rule Set, instead of being compiled on the server."
First of all Mod Security is in that version using the obsolete 2.9.8 and the even more obsolete Owasp CRS 3.3.2, which in no way is "the latest" of anything and thereby providing a false sense of safety for the users, as no updates of the rules are made and the existing 3.3.2 rules are all the way back from 2021 - latest 3.x rules are 3.3.10 and they became obsolete end Q3 2026 and can therefore not be updated in any way, although it is stated in the interface of CWP
Furthermore - if a customer makes a manual update of the rules, eg from 3.3.2->3.3.10, the update is overwritten every night by CWP cron job and reverted to the obsolete 3.3.2 rules
In these days, where an updated Mod Security can make the difference between a compromised server and a working server that rejects attempts not wanted, it is very strange that the CWP team still insists on using the obsolete tools....?
If the new motto for CWP is that all apps should always use latest versions, it seems that securitywise, Mod Security is the place to put any work efford right now, to get all the old rules and modsec versions thrown out of the system, just like the old internal 7.x version was thrown out some weeks ago from obvious reasons....
I loaded my own updated of CRS months ago and I maintain the rules, updates, plugins and configs. CRS out the box is very strict, so needs some tweaking. This is why Comodo was so popular for being more application aware, CRS requires you to be aware of your applications.
v4.25.2 LTS is what I am using with a massive custom ruleset built over months of work, some customer annoyance to start. But rather an annoyed customer than a compromised one.
I fully agree - the correct version of the used Owasp CRS rules should be 4.25 or newer if available
I also agree, that CWP should take the big step and upgrade Mod Security from 2.9.8 to 2.9.15 or newer if available
But - until that step has been taken, CWP outta at least make sure that the delivered version on the servers aren“t completely obsolete version like 2.9.8 modsec (from 2024) + 3.3.2 owasp crs (from 2021) that is maintained and installed on the server
Also make sure that a newer version of the CRS rules are not just overwritten by an obsolete rules version, as it happens right now
Many administrators rely on what they see in the interface, and if the CWP interface assures them that an app is regularly updated to the newest version by directly writing it in the interface, this really need to be a given fact and not just a wrong note - I know what averybody says: "Better check than being sorry", but not all lives by that fact and not all users of panels are hardcore professionals that know how to look behind the scenes...
In fact that is probably why they use a panel interface rather than using a less graphic one, like webmin/virtualmin or other
When it comes to security, it is really important, that if the manufacturer of a given product informs that the product has a given way of operating, the buyer really has to be able to rely on that information
A little like if a garage puts 10 year old tires on your car when you have actually ordered completely new tires and not the ones hidden way back in the garages old stock.....