Falang multilanguage for WordPress <= 1.3.52 - Missing Authorization to Translation Update and Information Exposure
Strategic Overview
- Status
- Patched in 1.3.53
- Affected Plugin
- Falang multilanguage for WordPress
- Affected Version
<= 1.3.52- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-6869
At a glance
CVE-2024-6869 is a medium-severity Missing Authorization vulnerability in the Falang multilanguage for WordPress WordPress plugin, affecting versions <= 1.3.52. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.3.53; sites on affected versions should update now. Disclosed August 2024, reported by Lucio Sá.
Vulnerability Overview
The Falang multilanguage for WordPress plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions in all versions up to, and including, 1.3.52. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update and delete translations and expose the administrator email address.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Falang multilanguage for WordPress <= 1.3.52 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Falang multilanguage for WordPress the fix is 1.3.53: builds <= 1.3.52 are affected, anything from 1.3.53 onward is not.
Remediation
Update to version 1.3.53, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Falang multilanguage for WordPress 1.3.53 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Falang multilanguage for WordPress
- 8.8CVE-2026-54805: Falang multilanguage… Privilege Escalation
CVE-2026-54805 - 8.1CVE-2025-58619: Falang multilanguage <= 1.3.65 PHP Object Injection
CVE-2025-58619 - 7.2CVE-2024-30495: Falang multilanguage <= 1.3.47 SQL Injection
CVE-2024-30495 - 6.1Falang multilanguage for WordPress < 1.3.18 Reflected XSS
- 5.4CVE-2023-37968: Falang multilanguage <= 1.3.39 CSRF
CVE-2023-37968 - 4.4CVE-2024-4417: Falang multilanguage for WordPress <= 1.3.49 Stored XSS
CVE-2024-4417 - 4.3CVE-2025-48285: Falang multilanguage <= 1.3.61 CSRF
CVE-2025-48285 - 4.3CVE-2024-37240: Falang multilanguage <= 1.3.51 CSRF
CVE-2024-37240
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C