Old WordPress core file not removed during update to v6.7
-
Wordfence has reported 45 issues with “Old WordPress core file not removed during update” – I am a new user and really have no idea how to deal with this. I don’t want to simply delete files without knowing the impact, why this is being reported and why this is happening in the first place.
Anyone else having this issue and know how to resolve?
Thanks!
-
Hi @steviek, thanks for reaching out!
I have seen one other issue with 45 files this update cycle from 6.6.x to 6.7, and these do happen from time-to-time during a WordPress core update but aren’t common to everybody. If you still receive this result after running another scan, it could be down to file/owner permissions on your server but if it’s a one-off (or at least the first time) then it was likely a temporary issue when the core update was done.
I’ve modified my response if you received a prior notification via email.
Could you please send us a diagnostic as we’ll be able to see which files were detected in the most recent scan from there. I now think it’s best to check if they are indeed core files before confirming they’re OK to ignore until the next update.
Visit the?Wordfence > Tools > Diagnostics?page. You can send the output to us at?wftest @ wordfence . com. 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
Many thanks,
Peter.
- You must be logged in to reply to this topic.
