• clmisi

    (@clmisi)


    I have a problem with alert emails that say that a plugin should be updated. It says: Vulnerability Severity: 6.4/10.0 (Medium) level, though i choose “critical” in the alert prefs.
    So in my case, the alert level adjustment seems not to work on any of the 6 sites i take care about as an admin.
    I don’t want to automate the plug-in updates. I do maintenance every 2 month.

    Has somebody an idea to solve this?
    Many thanks
    Clmisi

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @clmisi, thanks for getting in touch.

    This is an example of a “Critical” severity Wordfence alert, where a plugin version with an unpatched security vulnerability has been found installed on your site during a scan. The vulnerability is then given a rating out of 10 for how serious or easily exploitable it may be. You can click on the vulnerability information link provided in the scan result that will give you more information.

    Naturally we’d recommend updating any vulnerable plugin immediately to the patched (or most recent) version rather than wait until your update cycle comes around.

    Thanks,
    Peter.

    Thread Starter clmisi

    (@clmisi)

    HI @wfpeter,

    many thanks for your quick answer. What effect has the classification in the alert prefs to choose from?
    Again, it says vulnerability : medium, i get the e-mail anyway.

    You said, that you recommend updating any plugin immediately, so what is my choice then?
    It is my responsibility to decide to update in maintenance circles or not. I personally don’t like to be overruled by software.
    That would force many people to let the plugins be updated automaticaly, which is a security risc too because it could and did happen, that the complete site did work anymore after an update. That would be then out of my sight.

    kind regards
    Clmisi

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