I am getting 403 Forbidden messages in the Joomla 3.6.5 admin panel when I (as Super User) attempt to:

  1. Select any page from 2 to end
  2. Change the articles per page from the default 20
  3. Search for an article using the keyword search box
  4. Filter articles by article category

If I disable ModSecurity in cPanel I don't have this problem, but my hosting providers do not recommend disabling ModSecurity. The rule that is being triggered is:

Message: Access denied with code 403 (phase 2). Test 'ARGS:view|ARGS:tmpl|ARGS:layout' against '!(^[0-9a-z-:]+$|^$)' is true. [*** [id "390606"] [msg "Atomicorp.com WAF Rules - Virtual Just In Time Patch: Joomla ARG injection"] [severity "CRITICAL"] [MatchedString "filter[search]="]

I have no access to ModSecurity other than to enable or disable it in cPanel.

The weird thing is that this happens on two websites, using the same template, on my reseller account, but I don't get these problems on the reseller account website itself or any of its subdomains. But my hosting provider tells me that all ModSecurity rules are the same.

They also say "The problem is the Joomla installs are tripping over Mod_security rules in regards to Argument injections etc. this is because of the way Joomla is programmed and Mod_Security rules are saying this is not a secure way of doing it"

We've been going round and round in circles so I'm posting here in the hope that someone else may have had this issue and found a solution.

  • Did you eventually resolve this issue? Did you follow any of itoctopus' suggestions? Did you solve it a different way? Please don't leave this question abandoned. Feb 3, 2019 at 5:45

1 Answer 1


I don't think this problem happens for everyone. I think the specific search keywords that you are using are the problem - or maybe something else specific to your website(s) (perhaps a common plugin?). I tried the above pattern on 3 different sites on 3 different servers all running ModSecurity, but the rule (rule #390606) wasn't triggered.

Having said that, the only way to get rid of the problem is to whitelist the rule in the whitelist.conf file (see here) - but I doubt that the hosting company will accommodate that request, because they will think (and rightly so) that this whitelisting will negatively impact the security on their servers. You can always try though - but - to be honest, I wouldn't stay with a host who accommodates such a request.

ModSecurity is becoming more and more aggressive, and probably the best way to deal with its false alarms is to have your own VPS, and then you can whitelist those rules.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.