Critical Security Issues Detected by Wordfence in Plugins and Files

  • Hi there,

    I recently conducted a security scan using Wordfence, and it flagged several critical issues that I need assistance with. Here’s a summary of what was detected:

    Malicious or Unsafe Files:

    Wordfence flagged two files within the Wordfence Activator plugin:
    File: wp-content/plugins/wordfence-activator/main.php
    File: wp-content/plugins/wordfence-activator/functions.php
    Both files were marked as “Critical” with potential security risks, but I’m unsure how to address them or if they should be deleted or repaired.
    Vulnerable Plugin:

    Plugin: “WP Affiliate Platform”
    Issue: Wordfence identified this plugin as having a security vulnerability, which it flagged as critical. I’d like to know if this can be resolved by updating, or if removing the plugin is recommended.
    Outdated Plugin:

    Plugin: “WordPress Automatic Plugin” (version 3.99.0 -> 3.107.0)
    This plugin was flagged for needing an upgrade. The issue was rated as “Medium.” I’d like to confirm if simply updating this plugin will resolve the issue without any compatibility risks.
    I’d greatly appreciate guidance on the safest steps to take to resolve these issues, particularly for the critical flags. If there are specific actions I should take within Wordfence or any alternative solutions, please advise.

    Thank you for your assistance!

    Contact Information (optional): If you need further information, feel free to contact me at [email redacted by moderator]

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

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

  • Hey @johnmendezmog,

    Please allow me to help.

    Solutions:

    1. Malicious or Unsafe Files: It appears you’re using a nulled plugin or a plugin purchased from a non-authorized 3rd-party. The activator files are one of the key indicators. Never use nulled plugins. Delete your nulled version of Wordfence (perform a clean uninstall) and the activator plugin (check your database for remnants), clear all cache layers, then install Wordfence Free from www.remarpro.com or purchase Wordfence Premium from wordfence.com.
    2. Plugin: “WP Affiliate Platform”: Update the plugin to the latest version (V6.5.2 of higher), clear all cache layers, and re-scan affected site(s) using a clean (not nulled) copy of Wordfence. Here’s some good info: Click here and here.
    3. Plugin: “WordPress Automatic Plugin”: This is normal and indicates Wordfence is working as intended. Update the plugin to the latest version (V3.107.0 or higher). clear all cache layers, and re-scan affected site(s) using a clean (not nulled) copy of Wordfence. You should have no conflicts. If any, contact the developers of that plugin for a fix or revert back to V3.99.0 until they fix the plugin.

    If satisfied with the above, please consider closing this topic as “Resolved.”

    Note: I’m not affiliated with Wordfence. Simply offering goodwill assistance.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @johnmendezmog, thanks for reaching out.

    Naturally the forums are open for the community to assist and I think @generosus has come up with some solid recommendations.

    Whilst the /wordfence-activator path does look like an externally sourced version of Premium may have been installed on your site at some point, we’re always mindful that developers or other freelancers can sometimes call the shots with this on behalf of their customers. As you’d be unable to fully benefit from scans, the latest malware signatures, or plugin updates, it’s best to revert to Wordfence Free as outdated plugins can pose a security risk in themselves.

    The free version of Wordfence includes a high percentage of the base features our paid services do, which we are proud to provide for the good of the wider WordPress community. Running that version going forward should still provide solid protection and continue to detect plugin issues like the ones you’ve seen above.

    Many thanks,
    Peter.

    Hey @wfpeter,

    I appreciate you and your support. If you ask me, you should consider closing topics as “Resolved” if no reply received from the topic originator within five (5) business days once an answer has been provided to the topic originator. It makes you look good and helps the community recognize that you’re working hard to support Wordfence and its customers.

    Cheers!

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