This same situation happened to me last week and it took my hosting company a few days to fix it.
This is what they said:
“Path for wordfence-waf.php file is not updated. I have updated the path in .user.ini which fixed the issue.”
We haven’t changed anything on the site for the past year, and hadn’t updated any plugins in the past couple weeks. Any idea what happened and how to prevent it in the future?
On a related note, I logged in to update the site and had a notice to Optimize Wordfence Firewall. It had this message:
To make your site as secure as possible, the Wordfence Web Application Firewall is designed to run via a PHP setting called auto_prepend_file, which ensures it runs before any potentially vulnerable code runs. This PHP setting is currently in use, and is including this file:
/home/users/web/b1402/###/###.com/wordfence-waf.php
If you don’t recognize this file, please contact us on the WordPress support forums before proceeding.
You can proceed with the installation and we will include this from within our wordfence-waf.php file which should maintain compatibility with your site, or you can opt to override the existing PHP setting.
This is the file that had the bad path in the users.ini file. How should I proceed?