Wordfence marking plugin updates as errors

  • Resolved mieche

    (@mieche)


    4 months ago

    Hello,

    I’m new Hide My Ghost, but have been using it on a site that was having a lot of hack attempts and love it. I have noticed over the last few months that everytime Hide My Ghost is updated I get a Medium Severity Problem warning from Wordfence for 20+ files related to Hide My Ghost.

    When I login to read the issue this is what Wordfence has in its Details: This file belongs to plugin “Hide My WP Ghost Lite” version “5.1.03” and has been modified from the file that is distributed by www.remarpro.com for this version. Please use the link to see how the file has changed. If you have modified this file yourself, you can safely ignore this warning. If you see a lot of changed files in a plugin that have been made by the author, then try uninstalling and reinstalling the plugin to force an upgrade. Doing this is a workaround for plugin authors who don’t manage their code correctly.

    Is this normal? Or is there something I need to change?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Peter

    (@petersquirrly)

    ??Hi Mieche,

    We appreciate taking the time to reach out to us!

    Feel free to ignore this, as it doesn’t affect your website security in any way. Most likely Wordfance saw that the plugin changed or was looking for something that isn’t there anymore any it gave you a notification, but there is no need to do anything and the security remains the same.

    If anything else comes up, we are one message away.

    Thread Starter mieche

    (@mieche)

    Thank you! Weird how it keeps happening, but glad to know it isn’t a real issue.

    Plugin Support Peter

    (@petersquirrly)

    We’ll try and reach out to them to see if anything can be done about it, but for the moment, ignoring it is the best way to go about it.

    Thread Starter mieche

    (@mieche)

    Awesome, thank you for the quick help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.