CVE-2021-24721: The Loco Translate WordPress plugin before 2.5.4 mishandles data inputs which get saved to a file, which can b

Q: How do I fix CVE-2021-24721?

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

Q: Is CVE-2021-24721 being exploited?

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

Q: What does CVE-2021-24721 affect?

CVE-2021-24721 affects loco translate. Severity is medium (CVSS 6.5). The Loco Translate WordPress plugin before 2.5.4 mishandles data inputs which get saved to a file, which can be renamed to an extension ending in .php, resulting in authenticated "translator" users being able to inject PHP code into files e

Q: How urgent is CVE-2021-24721?

Priority 43/100. Public exploit reference

This month

MEDIUM 6.5UPGRADE

CVE-2021-24721 is a medium-severity flaw (CVSS 6.5) 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.5.4 mishandles data inputs which get saved to a file, which can be renamed to an extension ending in .php, resulting in authenticated "translator" users being able to inject PHP code into files ending with .php in web accessible locations.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-94
Published	2021-11-08
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: loco translate project

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

Am I affected?

Timeline

2021-11-08 18:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

loco translate project loco translate UPGRADE

Affected: < 2.5.4

Fixed in: 2.5.4

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.5.4 (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.

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-2021-24721?

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

Is CVE-2021-24721 being exploited?

CVE-2021-24721 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-2021-24721 affect?

CVE-2021-24721 affects loco translate. Severity is medium (CVSS 6.5). The Loco Translate WordPress plugin before 2.5.4 mishandles data inputs which get saved to a file, which can be renamed to an extension ending in .php, resulting in authenticated "translator" users being able to inject PHP code into files e

How urgent is CVE-2021-24721?

Priority 43/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

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

References

← Back to latest CVEs