Title: wordpress_logged_in
Last modified: September 30, 2023

---

# wordpress_logged_in

 *  Resolved [treslabs](https://wordpress.org/support/users/treslabs/)
 * (@treslabs)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/wordpress_logged_in/)
 * Hi, Thanks for a great product and support. I was the person who suggested the
   blank post request setting. 🙂
 * We had a website that was recently hacked that is running Wordfence. For some
   reason the guy was able to traverse directories in the wp-content folder and 
   put his files everywhere. Is there a setting we missed in WF?
 * My suggestion is to add an option for wordpress_logged_in so that hacks are restricted
   to access via the login creds. I’m not a programmer so I’m not sure if it will
   truly help but it seems logical.
 * Aaron
 *     ```wp-block-code
       <IfModule mod_rewrite.c>
         RewriteEngine On
         RewriteCond %{HTTP_COOKIE} !.*wordpress_logged_in.*$ [NC]
         RewriteCond %{REQUEST_URI} ^(/.*?)/wp-content/uploads/.* [NC]
         RewriteRule . http://%{HTTP_HOST}%1/wp-login.php?redirect_to=%{REQUEST_URI} [L,QSA]
       </IfModule>
       ```
   

Viewing 1 replies (of 1 total)

 *  Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * (@wfpeter)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/wordpress_logged_in/#post-17092978)
 * Hi [@treslabs](https://wordpress.org/support/users/treslabs/), glad to hear you’ve
   been enjoying Wordfence and are an active customer in helping us improve security
   for all WordPress users!
 * There are “Directory Traversal” rules enabled by default in **Wordfence > All
   Options > Advanced Firewall Options > Rules**. However, if a person or bot was
   able to _write_ files rather than just traverse the directories with view permissions
   from a browser, another attack vector may have been used. There are naturally
   methods outside of WordPress that we don’t control like database passwords, cPanel
   access and FTP credentials so **as a rule, any time I think someone’s site has
   been compromised I also tell them to update their passwords for their hosting
   control panel, FTP,  WordPress admin users, and database if they haven’t already.**
 * Were you running the latest version of Wordfence, other plugins, and your theme
   at the time of the incident?
 * Many thanks,
   Peter.

Viewing 1 replies (of 1 total)

The topic ‘wordpress_logged_in’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [hacked](https://wordpress.org/support/topic-tag/hacked/)
 * [wp-content](https://wordpress.org/support/topic-tag/wp-content/)

 * 1 reply
 * 2 participants
 * Last reply from: [wfpeter](https://wordpress.org/support/users/wfpeter/)
 * Last activity: [2 years, 8 months ago](https://wordpress.org/support/topic/wordpress_logged_in/#post-17092978)
 * Status: resolved