Title: Modified Plugin File: NOT Modified
Last modified: March 16, 2017

---

# Modified Plugin File: NOT Modified

 *  [Pete Hahn](https://wordpress.org/support/users/dryheat3/)
 * (@dryheat3)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/modified-plugin-file-not-modified/)
 * Sorry if this was posted before but the search box at the top of the page does
   a google search of the entire WordPress.org and not just this particular forum.
   Someone might want to address that.
    I’ve been using Wordfence about 1 week. 
   After a scan runs I find it frequently picks up so called modified plugin files.
   However when I research things further I find that the plugin was recently updated
   and the Wordfence scan is still picking up the previous version and comparing
   two different versions. This occurs with several plugins so we can just blame
   this on a lazy plugin manager. After a couple of days the scan clears out the
   errors once the Wordfence scan is able to read from the current version. Not 
   a critical flaw, but this is annoying and there should be some way to address
   this more gracefully.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [mountainguy2](https://wordpress.org/support/users/mountainguy2/)
 * (@mountainguy2)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/modified-plugin-file-not-modified/#post-8929483)
 * The plugin scan is lame in my opinion. I just leave it unchecked. If someone 
   gets root on your WordPress install and starts modifying plugins, you probably
   don’t need a Wordfence scan to tell you that’s going on. In my opinion, organizing
   and tweaking a variety of website backups is better than spending time messing
   around with Wordfence scanning issues. MTN
 *  Plugin Support [wfphil](https://wordpress.org/support/users/wfphil/)
 * (@wfphil)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/modified-plugin-file-not-modified/#post-8940511)
 * Sometime it can be the case that some developers do not follow the official guidelines
   that WordPress provides for plugin developers by adding new code to an existing
   release.
 * In cases like this Wordfence will alert you to the fact that the plugin code 
   you have does not match what is in the repository. That is why we recommend you
   always use the feature that Wordfence provides to view changes in your plugin
   files before take any action – because it may just be a case of a developer who
   is not managing their code correctly.
 * Send the developer a message asking them if this is what has happened.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Modified Plugin File: NOT Modified’ 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/)

 * 2 replies
 * 3 participants
 * Last reply from: [wfphil](https://wordpress.org/support/users/wfphil/)
 * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/modified-plugin-file-not-modified/#post-8940511)
 * Status: not resolved