I have a Magento 2 site hosted on a VPS with Plesk. A few days ago both frontend and backend showed error 404. After taking the time to understand the problem, without success, I contacted my hosting provider who after a check identified the problem in "mod security". Then I initially disabled mod security and the site is visible again without any error.

The log error shows this type of error(my site oscured with xxx):

[Mon Jun 24 17:38:00.572617 2019] [:error] [pid 568:tid 140699999577856] [client] [client] ModSecurity: Warning. Pattern match "(?:'\\\\xbf?\\\\x22|\\\\x22\\\\xbf?'|^\\\\+?$)" at REQUEST_COOKIES:mage-messages. [file "/etc/apache2/modsecurity.d/rules/comodo/02_Global_Generic.conf"] [line "199"] [id "211290"] [rev "3"] [msg "COMODO WAF: XSS and SQLi vulnerability||www.xxxxx.it|F|2"] [severity "CRITICAL"] [tag "CWAF"] [tag "Generic"] [hostname "www.xxxxxx.it"] [uri "/customer/section/load/"] [unique_id "XRDuWM@02LUAAAI4PUkAAACX"], referer: https://www.xxxxxxxxx.it/

Here my questions, since it seems to be an important vulnerability:

  1. Does this vulnerability depend on a Magento 2.3.1 bug?
  2. in this case, what is the best configuration for mod security?

Thank you


Most likely not a good idea to disable Mod Security completely.

Best course of action would be to ask your hosting provider to turn it back on and to only whitelist rule 211290

| improve this answer | |
  • Hi, this thing has already been done. I would like to go further and see if there is a different solution. – Joso Jun 26 '19 at 6:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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