Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-0765: The Loco Translate WordPress plugin before 2.6.1 does not properly remove inline events from elements in the s

46
This month
MEDIUM 5.4UPGRADE

CVE-2022-0765 is a medium-severity flaw (CVSS 5.4) affecting loco translate. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Loco Translate WordPress plugin before 2.6.1 does not properly remove inline events from elements in the source translation strings before outputting them in the editor in the plugin admin panel, allowing any user with access to the plugin (Translator and Administrator by default) to add arbitrary javascript payloads to the source strings leading to a stored cross-site scripting (XSS) vulnerability.

Why this priority

  • EPSS top 10%: very likely to be exploited
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score5.4 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionRequired
EPSS exploit chance3.8% (top 10%)
CISA exploited listNo
WeaknessCWE-79
Published2022-04-18
Last modified2026-06-17
Publisher (CNA): WPScan · Vendor: loco translate project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

loco translate project loco translate UPGRADE
Affected: < 2.6.1
Fixed in: 2.6.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy loco-translate || rpm -q loco-translate || loco-translate --version
2. UPGRADE to 2.6.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade loco-translate
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade loco-translate
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-0765?

loco translate: upgrade to 2.6.1. Exact commands for each OS are on this page.

Is CVE-2022-0765 being exploited?

CVE-2022-0765 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-0765 affect?

CVE-2022-0765 affects loco translate. Severity is medium (CVSS 5.4). The Loco Translate WordPress plugin before 2.6.1 does not properly remove inline events from elements in the source translation strings before outputting them in the editor in the plugin admin panel, allowing any user with access to the plu

How urgent is CVE-2022-0765?

Priority 46/100. EPSS top 10%: very likely to be exploited; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.