• Resolved adambs

    (@adambs)


    My Wordfence scan has notified me that there are over 2500 files with issues. Lots of these are listed as unknown files in WordPress core, and there also many old WordPress files note removed during update. The unknown files are listed as high severity problem. When I click on details against each of these unknown files in the list in the Wordfence dashboard, it says “This file is in a WordPress core location but is not distributed with this version of WordPress. This scan often includes files left over from a previous WordPress version, but it may also find files added by another plugin, files added by your host, or malicious files added by an attacker.”

    The files listed as old WordPress files are listed as low severity problem.

    How can i resolve these issues?

Viewing 15 replies - 1 through 15 (of 28 total)
  • Hello.
    We’ve got notifications for a few sites this morning. Same issue.
    E.g. Unknown file in WordPress core: wp-admin/about.php

    1000’s of false flags?

    Hi there,

    Same issue here, Wordfence is reporting over 2400 unknown files (or old files not removed) in the WordPress core, mainly centred around the WordPress includes folder. It is only occurring on one of our sites, other sites appear to be unaffected. All sites are fully up to date running WordPress V6.7.

    lauramcmillancreative

    (@lauramcmillancreative)

    Same issue here. 2504 errors.

    High Severity Problems:

    • Unknown file in WordPress core: wp-admin/about.php
    • Unknown file in WordPress core: wp-admin/admin-footer.php
    • Unknown file in WordPress core: wp-admin/admin-header.php

    etc.

    Running WordPress 6.7, which updated last night around 23:00 GMT. WordFence ran the scan and reported problems at 04:53 GMT.

    Cloned the site to test deletion and used the ‘Delete all deletable files’ function and it completely broke the site.

    Haven’t seen this issue on any of my other sites yet.

    I just scan the site and it show all the worpress files as Unknown file in WordPress core where as i just install new wordpress

    lauramcmillancreative

    (@lauramcmillancreative)

    Update:
    Updated one of my other sites to WordPress 6.7 and had all the same issues crop up. So this seems to be an issue with updating to the latest version of WordPress. There were none of these issues there previously.

    Same here! Repair files is not possible and deletion of the files breaks the sites.

    What’s happening?

    Just adding in that I am having the same issue so I can get notified via email when there are replies.

    I am experiencing the same issue with unknown files appearing in my WordPress core after a recent update. Files like wp-includes/meta.php.orig and others have been flagged, and I’m not sure if they are safe to delete. Any guidance on resolving this would be much appreciated.

    i am facing the same issue here.

    after updating to 6.7 wordpress version, over 1000 red flags. If i delete the files , the site brakes into 403 error.

    what is happening??

    I can confirm.. I have over 50 sites having these false positives after updating to WP 6.7 yesterday.

    I have the same problem after updating to WP 6.7

    intelliproductions

    (@intelliproductions)

    Seems that Wordfence is not yet familiar with WordPress 6.7.

    Same here.

    Same issue on multiple sites I upgraded yesterday to 6.7. Looking forward to a resolution.

    I’m also having this issue on one of my sites, running 6.7. However, other sites of mine, on the same host and running 6.7 don’t have this issue. I’m monitoring the situation and trying to see what differences there might be be.

    Just to note, inspecting the flagged files seems to show they ARE WordPress core files, although I haven’t checked them all!

    Carlos Blázquez

    (@carlosblazquez4global)

    +1 here.

    This world class bug makes WordFence unusable, so we are waiting for news of plugin support that has not yet appeared…

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