Scan reports 57 old WordPress files left over after 6.2 upgrade – legit?
-
So after my site auto-updated to 6.2, WordFence ran an autoscan and reported no less than 57 WordPress Core files left over.
Old WordPress core file not deleted during update: wp-includes/Requests/Cookie/Jar.php
Type: FileI’ve had these scan results before, but usually with 1 or 2 files. This is a whole other order of magnitude. I can bulk-delete the reported files, but am worried that WordFence may be wrong here, and that the reported files are still part of Core.
This is a selection of the files reported:
wp-includes/Requests/Cookie/Jar.php
wp-includes/Requests/Auth.php
wp-includes/Requests/Cookie.php
wp-includes/Requests/Exception/HTTP/30x.php (multiple)
wp-includes/Requests/Exception/HTTP/40x.php (multiple)All these look to me like legit WP files, and improble that a minor release like 6.2 would move or rename all of them.
Is WordFence right here? How can I find out for myself?
The page I need help with: [log in to see the link]
- The topic ‘Scan reports 57 old WordPress files left over after 6.2 upgrade – legit?’ is closed to new replies.