Incompatibility with WordPress 5.8 new widget block editor.
-
I went to look at my widgets last night.Just look at them, I had no intention of changing anything. But WordPress 5.8’s new widget block editor couldn’t locate the WOOF widget. The widget disappeared from my site and in the middle of trying to restore it the server blocked my access.
According to my host’s tech support, they found this in the logs
csf.deny: 69.14.###.### # lfd: (mod_security) mod_security (id:212740) triggered by 69.14.###.### (US/United States/d14-69-236-154.try.wideopenwest.com): 5 in the last 3600 secs - Sat Jul 31 03:42:14 2021
(I obscured my ISP address)
My hosts said the IP was blocked when ModSecurity WAF triggered a block due to a pattern that is usually used for XSS attacks by hackers or attackers. It could be a false positive alert as well sometimes. The related logs for the trigger is as below.
Request: GET /wp-content/plugins/woocommerce-products-filter/ext/by_text/css/by_text.css?ver=1.2.5.3 Action Description: Access denied with code 403 (phase 2). Justification: Test 'REQUEST_URI|ARGS_POST|ARGS_NAMES|REQUEST_COOKIES|REQUEST_COOKIES_NAMES|XML:/*|!ARGS:/body/|!ARGS:/content/|!ARGS:/description/|!ARGS:Post|!ARGS:desc|!ARGS:emailglobalheader|!ARGS:html_message|!ARGS:text|!REQUEST_COOKIES:/__utm/|!REQUEST_COOKIES:/_pk_ref/|!ARGS_POST:format|!ARGS:emailglobalheader' against '@rx image\/svg\+xml|text\/(?:css|html|(?:x-)?(?:(?:ecma|java|vb)script|scriptlet)).|.application\/x-shockwave-flash' is true.
This has never happened before. And I had to install The Classic Widget Editor plugin in order to restore the WOOF widget to my shop page. So I’m attributing it to an incompatibility with WordPress 5.8’s new new widget block editor.
- The topic ‘Incompatibility with WordPress 5.8 new widget block editor.’ is closed to new replies.