Plugin Support
wfphil
(@wfphil)
Hi @listafriikki
I see that you have expanded editor functionality, which I presume is being provided by another plugin. If that is the case then it appears that plugin has generated a request that the Wordfence firewall blocked. The block is caused by the option Monitor background requests from an administrator’s web browser for false positives >> Admin Panel found in the Allowlisted URLs section on the All Options page. Below is our documentation for this option:
https://www.wordfence.com/help/firewall/options/#monitor-background-requests
Hi there,
And thank you for your response.
We indeed do have Classic Editor plugin, but it’s been there for at least over a year, and this thing happened yesterday.
So are you suggesting we should allowlist it? Or should we be worried about it?
I don’t know if it matters, but our theme is SociallyViral: just wanted to let you know.
I also noticed on the Live Traffic, that Wordfence had blocked someone from China and it also had that Ajax.php mentioned on it. But it happened later on yesterday.
But anyways, I would appreciate if you could let us know whether there’s nothing to worry about or can we just allowlist it.
Plugin Support
wfphil
(@wfphil)
Hi @listafriikki
Thank you for the update.
Going back to my original reply, your screenshot shows that you have extended editor functionality, which I presume is being provided by another plugin. If that is the case then it appears that plugin has generated a request that the Wordfence firewall blocked. You can use the option to add the block to the allowlist.
You can share a screenshot of your Live Traffic page if you wish to.