CVE
Translate and boost SEO – Automatic AI translation – wpLingua stored XSS in translated page output
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.0 or later
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. wpLingua plugin version 3.1.1 or earlier
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
Who should check
Sites running the wpLingua 'Translate and boost SEO' WordPress plugin version 3.1.1 or earlier.
Read the source excerpt
“Plugin <= 3.1.1 is vulnerable to a medium priority Cross Site Scripting (XSS)”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
wpLingua plugin version 3.1.1 or earlierUpgrade to a fixed version: 3.2.0 or later.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- wplingua
through 3.1.1
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124410
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: cve.now feed data
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: patchstack.com
Which versions are affected by CVE-2026-124410?
wplingua: through 3.1.1.Source: cve.now feed data
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: patchstack.com
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: patchstack.com