Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97020 Overview
CVE-2026-97020 is a Stored Cross-Site Scripting (XSS) vulnerability in the PO/MO Editor plugin for WordPress, affecting all versions up to and including 1.4.2. The flaw stems from insufficient input sanitization and output escaping on the podata parameter. Authenticated attackers with subscriber-level access or higher can inject arbitrary JavaScript that executes when users load affected pages. The injected payload is served as a replacement .po/.mo translation file through the plugin's own load_textdomain_mofile filter, causing WordPress to render attacker-controlled strings in place of core translations [CWE-79].
Critical Impact
Low-privileged users can store JavaScript that executes in the context of any visitor, enabling session theft, account takeover, and defacement across the WordPress site.
Affected Products
- PO/MO Editor plugin for WordPress — all versions through 1.4.2
- WordPress sites allowing subscriber-level registration with this plugin installed
- Any site using the plugin's load_textdomain_mofile filter integration
Discovery Timeline
- 2026-10-14 - CVE-2026-97020 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-97020
Vulnerability Analysis
The PO/MO Editor plugin provides an interface for editing WordPress translation files directly from the admin dashboard. The vulnerability resides in how the plugin processes the podata parameter submitted during translation editing operations. The plugin stores user-supplied translation content without sanitizing script-bearing payloads, then re-serves that content via its load_textdomain_mofile filter hook. When WordPress requests a translated string, the filter returns the attacker's replacement file, and the malicious content is rendered inline on affected pages.
Because the payload is injected into translation strings consumed by core and theme code paths, execution occurs in the browser of any user who loads a page that resolves the hijacked textdomain. The scope change reflects the fact that the injected code executes in a context broader than the plugin itself, affecting arbitrary WordPress-rendered pages.
Root Cause
The root cause is missing input validation on the podata parameter combined with absent output escaping when the stored content is written to disk as a translation file and later served to end users. The plugin trusts authenticated input and treats arbitrary strings as valid gettext data. See the plugin's class-pomoeditor-manager.php at lines 41, 110, 115, and 177, and class-pomoeditor-system.php at line 78, referenced in the Wordfence Vulnerability Report.
Attack Vector
An attacker authenticates to WordPress with at least subscriber privileges, then submits a crafted podata payload containing HTML or JavaScript. The plugin writes the payload into a .po/.mo file and registers it through the load_textdomain_mofile filter. Subsequent requests that trigger the affected textdomain cause WordPress to substitute the attacker's translated string into the rendered output, executing the script in each visitor's browser session.
See the plugin source at class-pomoeditor-manager.php line 110 and class-pomoeditor-system.php line 78 for the vulnerable handlers.
Detection Methods for CVE-2026-97020
Indicators of Compromise
- Unexpected .po or .mo files in the WordPress wp-content/languages/ directory or plugin-managed translation paths, especially files containing <script> tags or HTML markup
- Modifications to translation files timestamped after subscriber-level account activity
- Outbound requests from visitor browsers to attacker-controlled domains originating from pages that load WordPress translations
- New or modified subscriber accounts followed by activity against the PO/MO Editor admin endpoints
Detection Strategies
- Scan .po and .mo files for HTML or JavaScript tokens such as <script, onerror=, onload=, javascript:, and eval(
- Monitor WordPress audit logs for POST requests to PO/MO Editor endpoints containing the podata parameter from non-administrative accounts
- Review load_textdomain_mofile filter output in staging environments to confirm translation integrity
Monitoring Recommendations
- Enable file integrity monitoring on the wp-content/languages/ directory and plugin translation directories
- Alert on any subscriber-tier user triggering plugin admin-ajax or REST routes exposed by PO/MO Editor
- Capture and inspect server access logs for repeated podata submissions or oversized translation payloads
How to Mitigate CVE-2026-97020
Immediate Actions Required
- Deactivate and remove the PO/MO Editor plugin until a patched release above 1.4.2 is confirmed available
- Audit all WordPress user accounts and remove unnecessary subscriber-level registrations
- Inspect existing .po/.mo files for injected scripts and restore clean copies from the originating plugin or theme packages
Patch Information
At the time of publication, no fixed version beyond 1.4.2 is referenced in the NVD entry. Monitor the Wordfence Vulnerability Report and the plugin's WordPress.org listing for a security release, and apply it as soon as it is published.
Workarounds
- Disable open user registration or restrict registration to trusted email domains to limit who can obtain subscriber access
- Apply a Web Application Firewall (WAF) rule to block POST requests containing <script, onerror, or onload tokens inside the podata parameter
- Set wp-content/languages/ and plugin translation directories to read-only for the web server user where operationally feasible
- Enforce a strict Content Security Policy (CSP) that disallows inline scripts to reduce the impact of injected payloads
# Example WAF rule concept (ModSecurity) to block script payloads in podata
SecRule ARGS:podata "@rx (?i)(<script|onerror=|onload=|javascript:)" \
"id:1026097020,phase:2,deny,status:403,log,\
msg:'CVE-2026-97020 PO/MO Editor podata XSS attempt blocked'"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

