CVE-2026-124410

WordPress Translate and boost SEO – Automatic AI translation – wpLingua plugin <= 3.1.1 - Cross Site Scripting (XSS) vulnerability

publishedCWE-79

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.

Technical severity7.1 highCVSS 3.1 · CNA: Patchstack

Published2026-11-13Source updated 2026-11-13

Collected2026-11-131 attributed source

Fixes and workarounds

Fix

Update the WordPress Translate and boost SEO – Automatic AI translation – wpLingua plugin to the latest available version (at least 3.2.0).

Source: CNA: Patchstack

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
Translate and boost SEO – Automatic AI translation – wpLingua wpLingua Translation Service `wplingua` https://wordpress.org/plugins	≥ 0; ≤ 3.1.1 (affected, custom); unaffected at 3.2.0 Other versions: unaffected	CNA: Patchstack

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / score	Vector	Authority
3.1 / 7.1 high	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`	CNA: Patchstack

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

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=cveCNA: Patchstack · vdb-entry

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API key Use x402 Connect an agent

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide