CVE-2026-94239 Loco Translate CVE debrief

Who should care

Defenders responsible for WordPress installations with the Loco Translate plugin should assess exposure and prioritize updating the plugin to 2.8.9 or later. They should also monitor admin pages for suspicious activity and restrict translator capability to trusted users to prevent potential Stored Cross-Site Scripting attacks against high privilege users.

Why it matters

Defenders should care about CVE-2026-94239 because it allows users with translator capability to perform Stored Cross-Site Scripting attacks against high privilege users, potentially leading to unauthorized admin page modifications. The vulnerability requires verification of the Loco Translate plugin version and monitoring of admin pages for suspicious activity.

• Potential for Stored Cross-Site Scripting attacks against high privilege users
• Risk of unauthorized admin page modifications
• Need for verification of Loco Translate plugin version
• Importance of monitoring admin pages for suspicious activity

Technical summary

The Loco Translate WordPress plugin before 2.8.9 does not sanitise and escape some bundle configuration values before outputting them back in an admin page, allowing users with the translator capability and above to perform Stored Cross-Site Scripting attacks against high privilege users such as administrators. This vulnerability requires defenders to prioritize verifying the Loco Translate plugin version and ensuring it is updated to 2.8.9 or later, as well as monitoring for suspicious activity on admin pages to prevent potential unauthorized admin page modifications.

Defensive priority

Defenders should prioritize verifying the Loco Translate plugin version and ensuring it is updated to 2.8.9 or later, as well as monitoring for suspicious activity on admin pages.

Recommended defensive actions

• Verify Loco Translate plugin version and update to 2.8.9 or later
• Monitor admin pages for suspicious activity
• Restrict translator capability to trusted users
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability, with the primary source being the WPScan reference. Defenders should verify the Loco Translate plugin version and ensure it is updated to 2.8.9 or later. The vulnerability allows users with translator capability to perform Stored Cross-Site Scripting attacks against high privilege users. Evidence is limited, and defenders should monitor admin pages for suspicious activity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.