You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The modsecurity web application firewall (WAF) which is often used in Apache and Nginx, prevents WP Githuber MD from working because it triggers a false positive due to the h2m_strip_tags argument.
The WAF see's the argument which contains the string strip_tags and thinks it's a PHP Injection Attack.
I'm reporting this, not necessarily because something should be changed/fixed in WP Githuber MD, maybe just to add it to the known issues.
To reproduce
Steps to reproduce the behavior:
Install modsecurity and modsecurity-crs
Install the wordpress-rule-exclusions-plugin for crs
Update a Wordpress page
Expected behavior
Ideally modsecurity wouldn't block the POST and would allow the user to post pages using WP Githuber MD
(see also coreruleset/wordpress-rule-exclusions-plugin#60 )
Describe the bug
The modsecurity web application firewall (WAF) which is often used in Apache and Nginx, prevents WP Githuber MD from working because it triggers a false positive due to the
h2m_strip_tags
argument.The WAF see's the argument which contains the string
strip_tags
and thinks it's a PHP Injection Attack.I'm reporting this, not necessarily because something should be changed/fixed in WP Githuber MD, maybe just to add it to the known issues.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Ideally modsecurity wouldn't block the POST and would allow the user to post pages using WP Githuber MD
Server environment
User environment
Additional context
Logs can be seen in the issue opened with the wordpress-rule-exclusions-plugin modsecurity CRS plugin coreruleset/wordpress-rule-exclusions-plugin#60
The text was updated successfully, but these errors were encountered: