• chins4

    (@chins4)


    After I updated to v6.4.2. Wordfence identified 71(!) old WordPress core files not removed. These errors/files do not appear on my staging site, only on my live site. Reading suggests that these files are best deleted for security, but as I can’t delete them on my staging site first (because Wordfence doesn’t identify the same errors/files on there), I’m a little hesitant to click ‘Delete All Deletable Files’ on my live site – even after backing it up.

    Is it safe to delete these files? Or is there a better solution to prevent this issue from occurring again at the next update?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support wfmark

    (@wfmark)

    Hi @chins4, thank you for reaching out.

    Sometimes updates can leave files present for various reasons, in most cases, it is safe to remove the files, but I recommend that you backup the site before removing or repairing any files found during a scan. 

    Would it be possible to send me a diagnostics report to wftest @ wordfence.com? You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,

    Mark.

    Thread Starter chins4

    (@chins4)

    Hi @wfmark

    Thanks for responding. Report sent!

    Tracy

    Plugin Support wfmark

    (@wfmark)

    Hi @chins4, Thank you for sending the diagnostic report.

    From the diagnostic, I see it’s mostly Random_compat files that are required by Wordfence for safe implementation of certain PHP functions.

    As you are running WordPress version 6.4.2, could you please update to the latest version 6.4.3.

    Once done, please run another scan and let me know whether you see the same scan results.

    Thanks,

    Mark.

    Thread Starter chins4

    (@chins4)

    Hi Mark

    Looks like the same issues on 6.4.3.

    I’ve sent another diagnostic report so you can see…

    Thanks

    Tracy

    Plugin Support wfmark

    (@wfmark)

    Hi @ chins4, Apologies for the delayed response.

    I forgot to turn on notifications for replies on this topic.

    Are you still having issues with this?

    If so, please send an updated diagnostic report to wftest @ wordfence.com. You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Thanks,

    Mark.

    Thread Starter chins4

    (@chins4)

    Hi Mark

    Yes, still happening. Sent the diagnostic report this morning.

    Thanks for following up!

    Tracy

    zainsht297

    (@zainabshoukat297)

    Old WordPress core file not removed during update

    I have shared the diagnostic report by email. please check and confirm should I delete the files?

    Thread Starter chins4

    (@chins4)

    Hi Mark

    Any update on this? It’s still happening…

    Thanks

    Tracy

    Generosus

    (@generosus)

    Hey @chins4,

    Update to WP 6.6.1, clear all cache layers, then run another scan. The issue should be fixed.

    If the above solved your issue, kindly close this topic as “Resolved.”

    Thank you!

    ————

    References:

    1. Old WordPress Core File Not Removed During Update
    2. WordFence Warning About Files Left Behind During the Update to WordPress 6.6.

    I have this same issue where I’ve upgraded to wordpress 6.7 and Wordfence is showing 45 old version files. I’m new to wordpress so how to clear all cache isn’t something I know how to do.

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