• Hey WordFencers,

    Thanks for WordFence… it rocks! I’m very grateful.

    One small issue though: I get lots of mail now about plugins that need an upgrade. Any chance of changing this to a warning, or including an option to disable the plugin version check? I don’t really consider out-of-date plugins a “critical” issue, but I do want to get email for other critical issues.

    Thanks,
    Graham

    https://wordpress.org/plugins/wordfence/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi,

    Maybe I can help clear up why we do that.
    Out of date plugins and themes are one of the top reasons you get hacked. I’ve never met a single security guy for WP that says its ok to run with those. The revslider for instance had a huge hole in it, which caused many people problems. It was patched in version 4.2. If we didn’t alert people to that critical warning, how many would still be hacked today? Hackers don’t wait around for you to find their exploits, they are constantly changing and modding their code to make it harder to find. They keep looking for holes, for doorways, for ways to cause problems. Plugins have to kept up to date or you run the risk of those very same hackers messing your site up. Security holes get patched, functionality is improved, new wordpress code is adhered to. All great reasons to update.

    If your problem is that you don’t want to know about it, then you can click the link under it to “ignore this issue” and it will go to the ignored issues tab.

    But, for the record, this is likely something we won’t change, because its just not what a responsible security company should do.

    tim

    Thread Starter Graham Stoney

    (@greyham)

    Thanks Tim. You’ve sold me. In fact, I’ll go a step further and install Advanced Automatic Updates so that my plugins are updated automatically. That should minimise the emails, and keep my sites secure.

    Cheers,
    Graham

    Thanks for understanding. We really want to keep you safe 🙂

    tim

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

The topic ‘Making outdated plugins a warning, instead of a critical problem’ is closed to new replies.