• Resolved exeyesoftware

    (@exeyesoftware)


    I got an email today from Wordfence Free warning of issues with a WordPress site I manage. Here is the relevant portion of the email:

    Medium Severity Problems:
    
    * The Plugin "Astra Pro" needs an upgrade (4.3.1 -> 4.3.1).
    
    https://wpastra.com/pricing/?utm_source=graupi-license-form&utm_medium=graupi-license-invalidation&utm_campaign=purchase-astra/#developers
    
    * The Plugin "Backuply" appears to be abandoned (updated January 1, 1970, tested to WP 6.0).
    1. Why does it want me to upgrade Astra Pro to the same version it is?
    2. Backuply is not abandoned. I paid for a subscription for it a few weeks ago, and use it daily.

    Should I ignore this email? Should I expect to continue to get false warnings in the future, or is this just a one-time hiccup?

    I use the paid version of Wordfence on my business site and am happy with it, and am using the free version on a client site, which is where this email came from. Is the free version going to continue to give me problems?

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @exeyesoftware, thanks for your question.

    The same event that triggers WP Cron to run a Wordfence scan most likely set off WordPress plugin auto-updates at the same time. If plugin updates complete while the scan is still running, the list of outdated plugins may list “new -> current” version numbers that match, so no action needs to be taken and they’ll clear at your next scan.

    Even though a 2-week-old Backuply version can be seen on the wordpress.org repository at WordPress > Plugins > Add New, it looks like their paid version is available separately to this. If it uses the WordPress Plugins API to display when it has updates and provides an empty date, that is what Wordfence sees. Plugins from outside the repository have to provide their own date, so it might be worth checking in with them to see if that’s an issue that needs to be rectified. As a temporary solution, you can safely ignore this result in Wordfence > Scan > Results Found.

    Thanks,
    Peter.

Viewing 1 replies (of 1 total)

The topic ‘Erroneous reports on plugin status’ is closed to new replies.