Hi @decwodie, thanks for getting in touch.
If you still receive this result after running another scan, it has been seen from time-to-time that issues with the WordPress core update process not completing fully, file access permissions on your server, or something just temporarily failed when the update was done.
For example, WordPress 6.6 had some files not flagged for removal as they should have been. It was corrected for the next release.
Make sure to back up your site first if you attempt to delete the listed files yourself. Alternatively, you can exclude results for “Old WordPress core file not removed during update” from future scan results in Wordfence > Scan by selecting Ignore > Ignore Until File Changes next to the result. This will ignore the file until further modifications are detected or a future WordPress update removes them.
Many thanks,
Peter.
Hi @decwodie,
If you don’t mind, please allow me to help.
In addition to what @wfpeter suggested, try the following:
- Option 1: Try this, clear all cache layers, then re-scan your site.
- Option 2: Re-install WordPress 6.7 from within your WP Dashboard, clear all cache layers, then re-scan your site.
- Option 3: If the above did not help, perform a plugin support topic search using the term “old wordPress core file not removed during update” for other potential solutions.
If satisfied with the above, kindly consider closing this topic as “Resolved.”
Cheers!
Note: I’m not affiliated with Wordfence. Simply offering goodwill support.
