Skip to main content
VulnerabilityPublished

CVE-2026-118047: Falang multilanguage for WordPress · Cross-site Scripting

Affects Falang multilanguage for WordPressSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 7 Nov 2026, 11:50 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
sboueyFalang multilanguage for WordPressAffected
  • <=1.4.6
Fixed in–

AI-suggested

Users should monitor the vendor's advisory channels for updates. In the meantime, restricting subscriber-level access and disabling or limiting use of the Falang plugin may reduce risk. Because the nonce is exposed via an unprotected AJAX handler, consider restricting access to that handler or applying custom input validation and output escaping as a temporary mitigation.

Description

The Falang multilanguage for WordPress plugin (versions up to 1.4.6) contains a stored cross-site scripting (XSS) vulnerability. Authenticated users with subscriber-level access or higher can exploit insufficient input sanitization and output escaping in a parameter used during term updates. The vulnerability allows injection of arbitrary scripts that execute when other users view the affected pages. The exploit is facilitated by a nonce exposed to any logged-in user via an unprotected AJAX handler, requiring no elevated privileges to obtain.

References

Community reviews

Loading reviews…