Wordfence Firewall /wp-content/wflogs/config.php file quarantined

Home Forums BulletProof Security Pro Wordfence Firewall /wp-content/wflogs/config.php file quarantined

Viewing 1 post (of 1 total)
  • Author
  • #29090
    AITpro Admin

    Wordfence recently created a new Firewall feature in the newest version of Wordfence, which is very similar to the BPS Pro Plugin Firewall|Plugin Firewall AutoPilot Mode, which was created in BPS Pro 3.5 years ago.  If you have both Wordfence and BPS Pro installed then the Wordfence Firewall may cause problems or break the BPS Pro Plugin Firewall.  We do not have enough information yet to determine what problems the Wordfence Firewall may create for BPS Pro.  BPS Pro AutoRestore|Quarantine quarantines this new Wordfence Firewall file:  /wp-content/wflogs/config.php, which contains this code below:

    <?php exit('Access denied'); __halt_compiler(); ?>

    This Wordfence file and code are not malicious. The Wordfence /wp-content/wflogs/config.php file is dynamically updated so an AutoRestore wp-content folder exclude rule needs to be created so that the Wordfence wflogs folder is not checked by AutoRestore|Quarantine. Do the steps below to create an AutoRestore wp-content folder exclude rule for the Wordfence wflogs folder.

    1. Go to the AutoRestore page and turn Off AutoRestore.
    2. Go to the Quarantine page and restore the wflogs files that were quarantined.
    3. Go back to AutoRestore > click on the Exclude wp-content Folders tab page > type or copy and paste the name of the wflogs wp-content folder: wflogs
    Note:  If you are using Wordfence caching then also create a wp-content folder exclude rule for the: wfcache folder.
    4. Click all 3 buttons in order 1, 2, 3: 1. click the Save To DB button, click the 2. Create Filter button and click the 3. Exclude Folders Now button.
    5. Turn AutoRestore back on.

    Additional Wordfence Firewall Problem:
    The Wordfence Firewall may add the code shown below or similar code to your Root htaccess file, which will trigger the Wordfence HUD check Error message below.  See solution below.

    HUD Check: Wordfence PHP/php.ini handler htaccess code detected
    Wordfence PHP/php.ini handler htaccess code was found in your root .htaccess file, but was NOT found in BPS Custom Code.
    Click Here for the steps to fix this Wordfence problem.
    CAUTION: Using the Wordfence WAF Firewall may cause serious/critical problems for your website and BPS Pro.
    To Dismiss this Notice click the Dismiss Notice button below. To Reset Dismiss Notices click the Reset|Recheck Dismiss Notices button on the S-Monitor page.

    Wordfence WAF Firewall Error

    # Wordfence WAF 
    <IfModule mod_suphp.c> 
    suPHP_ConfigPath '/home/oursite/public_html' 
    <Files ".user.ini"> 
    <IfModule mod_authz_core.c> 
    Require all denied 
    <IfModule !mod_authz_core.c> 
    Order deny,allow 
    Deny from all 
    # END Wordfence WAF

    The Setup Wizard is not designed to figure out that type of custom wordfence htaccess code since it is not standard PHP/php.ini handler htaccess code. So you will need to do these steps below to fix this problem.

    1. Copy the Wordfence WAF htaccess code to this BPS Root Custom Code text box: CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
    2. Click the Save Root Custom Code button.
    3. Go to the BPS Security Modes page and click the Root Folder BulletProof Mode Activate button.

    Additional Wordfence problems reported by numerous Wordfence users on the WordPress.org site:
    Wordfence Problem Versions: 6.1.2, 6.1.3, 6.1.4, 6.1.5 and 6.1.6
    A large number of Wordfence users are experiencing various serious to critical problems (website crashed, website not loading, etc.) with the new Wordfence WAF. It appears that Wordfence is scrambling to fix the bugs/coding mistakes and releasing back to back new Wordfence versions. At this time it is unknown if Wordfence will continue to release additional back to back versions or if the bugs/coding mistakes are all fixed. If you are using Wordfence then you should probably wait until all the dust settles before upgrading Wordfence on your website.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.