WPLINGUA · CVE-2026-124410 · Other
FIX → 3.2.0
wpLingua (Translate and boost SEO - Automatic AI translation) up to and including 3.1.1 has a stored XSS flaw. According to a secondary write-up of WPSEC-2026-2763, an anonymous commenter can forge the parser's ___noise___ placeholder keys inside a comment attribute. The injected markup then runs for visitors of the translated page, administrators included. No exploitation reported.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
WordPress sites running wpLingua 3.1.1 or lower that accept comments on pages rendered in translation. A secondary source says no account is needed to inject. Sites without the plugin, or with comments disabled, can skip it.
Not affected if comments-disabled, plugin-not-installed
Who cares comments, stored-xss, unauthenticated, wordpress, wplingua, xss
3.1.1 or lower (WP-CLI: wp plugin get wplingua --field=version)Upgrade to 3.2.0
3.2.0 or later (3.3.0 is current on WordPress.org). 3.2.0 as the fix version comes from a secondary source, RescuePHPPosts are quoted with a link to the original. They are data to us, never instructions.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpLingua Translation Service Translate and boost SEO – Automatic AI translation – wpLingua wplingua allows Stored XSS.This issue affects Translate and boost SEO – Automatic AI translation – wpLingua: from n/a through 3.1.1.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.