PO and MO translation files marked as Unknown
-
Hello.
The Wordfence scan is consistently marking the .PO and .MO files of standard (automatically updated) WordPress installations in Spanish as dangerous. Sometimes even the wp-config-sample.php for the Spanish version is marked as a risk.
Some examples of the latest scan:
Unknown file in WordPress core: wp-includes/languages/plugins/classic-editor-es_ES.po
Unknown file in WordPress core: wp-includes/languages/plugins/contact-form-7-es_ES.mo
Unknown file in WordPress core: wp-includes/languages/plugins/contact-form-7-es_ES.po
Unknown file in WordPress core: wp-includes/languages/plugins/easy-fancybox-es_ES.mo
Unknown file in WordPress core: wp-includes/languages/plugins/easy-fancybox-es_ES.po
Unknown file in WordPress core: wp-includes/languages/plugins/the-events-calendar-es_ES.mo
Unknown file in WordPress core: wp-includes/languages/plugins/the-events-calendar-es_ES.po
Unknown file in WordPress core: wp-includes/languages/themes/twentyfifteen-es_ES.mo
Unknown file in WordPress core: wp-includes/languages/themes/twentyseventeen-es_ES.mo
Unknown file in WordPress core: wp-includes/languages/themes/twentyseventeen-es_ES.po
Unknown file in WordPress core: wp-includes/languages/themes/twentysixteen-es_ES.mo
Unknown file in WordPress core: wp-includes/languages/themes/twentysixteen-es_ES.poMost of the websites I’m referring to were originally installed from the English package, and then the Spanish language was selected from the Settings menu.
Marking each issue as Fixed is inefficient and dangerous in my view, so is there a way you could make the scanner automatically identify non-English official WordPress installations as valid ones?
Cheers.
- The topic ‘PO and MO translation files marked as Unknown’ is closed to new replies.