False positive caused by Plesk WordPress Toolkit

  • Resolved zeno001

    (@zeno001)


    4 years, 4 months ago

    Just started getting what I think is a false positive on sites I manage using Plesk’s WorfPress Toolkit.

    This adds three DEFINEs to the top of the wp-config.php file:

    define('DISALLOW_FILE_EDIT', true);
define('CONCATENATE_SCRIPTS', false);
define('WP_AUTO_UPDATE_CORE', 'minor');// This setting is required to make sure that WordPress updates can be properly managed in WordPress Toolkit. Remove this line if this WordPress website is not managed by WordPress Toolkit anymore.

    …but Wordfence has just reported this on three sites as being malicious. I have not changed anything recently but it looks like Wordfence has just started reporting this as malicious.

    I’ve checked the file and it all seems OK so this looks like a false positive.

    Getting this on three Wordfence Premium sites but NOT on at least one with the free version of Wordfence, so was there an update today to the Premium version that is causing this?

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

  • Thanks for reaching out.

    This was due to a scan signature that was pushed out yesterday. The signature was marked to “log only” again and it should not show up in future scans. Since the free sites get their rules after 30 days and premium sites get them immediately, the free ones didn’t alert yet. Again, this has already been addressed and shouldn’t alert in scans soon.

    Tim

    Thread Starter zeno001

    (@zeno001)

    Thanks for the explanation, Tim.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘False positive caused by Plesk WordPress Toolkit’ is closed to new replies.