WordPress 5.1 – unknown core files

Same here.

I also got this. I am hoping this is a false positive because of some upgrade in 5.1.

Me too, on 2 of my sites so far. Both sites are hosted on Lunarpages. What about you folks?

• This reply was modified 5 years, 9 months ago by lazykins. Reason: additional info added about websites affected

Well shoot I had Wordfence go ahead and delete those files, then I thought about the update I did the night before. I am going to ask wordfence to review and restore if advisable. I would hate to lose improved functionality from the update. Apparently Wordfence support is found by contacting/posting here.

• This reply was modified 5 years, 9 months ago by betterandless.

I checked a few of my sites and I believe those are old files, not new ones.

one thing I noticed is that the sites that have this issue were updated to WP 5.1 automatically (via Softaculous). I see no flagged files for the sites where I manually performed the update to WP 5.1. Must be a difference in the upgrade script (auto doesn’t clear these older files and Wordfence notices them as unneeded files). Can anyone else confirm this behavior?

If this is true it appears we can remove these 3 files (using Wordfence) with no adverse effect…

I also checked the official list of WordPress 5.1 files and these 3 files are on the list!

Unknown file in WordPress core: wp-includes/js/codemirror/jshint.js
Unknown file in WordPress core: wp-includes/js/tinymce/wp-tinymce.js.gz
Unknown file in WordPress core: wp-includes/random_compat/random_bytes_openssl.php

Version 5.1

I updated with Softaculous, and the next day had these files flagged by wordfence.

Looks like a Softaculous issue

https://www.ads-software.com/support/topic/unknown-files-flagged-after-botched-upgrade-to-wp-5-1/page/2/#post-11248928

My wordpress was upgraded by Installatron, not Softaculous, and I have the same issue with these 3 files, seemingly the last 3 listed to be removed in update-core.php.

I have the same three files, and I updated manually.

Phil here from the team at Installatron.

I can confirm these files were left behind by the WordPress 5.1 upgrade process. They’re present in WordPress versions up to and including 5.0.3.

Installatron’s update routine has been amended to clean up these files. If anyone has questions please open a support ticket:

https://installatron.com/tickets

Thanks!
Phil

thanks, Phil! That’s exactly what I needed to know. I’ve deleted those extra files (per WordFence’s recommendation) and feel better about your confirmation of that.

Thanks for confirming this, Phil.