The PO/MO Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'podata'…

Why it is Yellow

• CVSS 6.4 medium

References

• https://plugins.trac.wordpress.org/browser/pomo-editor/trunk/includes/class-pomoeditor-manager.php#L110
• https://plugins.trac.wordpress.org/browser/pomo-editor/trunk/includes/class-pomoeditor-manager.php#L115
• https://plugins.trac.wordpress.org/browser/pomo-editor/trunk/includes/class-pomoeditor-manager.php#L177
• https://plugins.trac.wordpress.org/browser/pomo-editor/trunk/includes/class-pomoeditor-manager.php#L41
• https://plugins.trac.wordpress.org/browser/pomo-editor/trunk/includes/class-pomoeditor-system.php#L78
• https://www.wordfence.com/threat-intel/vulnerabilities/id/a06e1a22-f660-401b-bfbf-0064a9220c26?source=cve

Original description

The PO/MO Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'podata' parameter in all versions up to, and including, 1.4.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is loaded as a replacement .po/.mo translation file via the plugin's own load_textdomain_mofile filter, causing WordPress to serve the attacker-written translation in place of the original core strings.