Hi @piotr2018wp,
Do your Wordfence scan results that detect these file changes give you any options to repair/remove the code or file(s) in question?
I would always recommend taking a full backup of your site before attempting to repair/remove. The backup should just ensure you can return the site to its previous state if anything about the removal stops your site from working properly.
Thanks,
Peter.
Yes but repairing was breaking my site’s admin page – try putting main index.php into wp-admin directory…
The only solution was ignoring but since I am administrating a dozen of sites the other users get annoyed 🙁.
Wordfence thinks that good wp-admin/index.php was modified because its content is checked against main index.php and I get that error on every site!
I think I should have written in the subject: False-positive High Severity Problem: “/wp-admin/index.php file has been modified”…
-
This reply was modified 2 years, 11 months ago by
piotr2018wp.
Hi @piotr2018wp, thanks again for the update.
I agree that the file shown matches (to the best of a manual side-by-side check with your screenshot) a seemingly valid /wp-admin/index.php whereas it seems to be checking against the main index as you mention.
Ignoring may be your most immediate best-case scenario to avoid somebody else with access from overwriting it, but could I see the scan result reporting this to see if there’s an obvious mismatch between the file location on the “Original Version…” vs. the “Modified Version…” shown?
Thanks again,
Peter.
