Translate Multilingual sites – TranslatePress <= 2.7.5 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.7.6
- Affected Version
<= 2.7.5- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-34827
At a glance
CVE-2024-34827 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the TranslatePress WordPress plugin, affecting versions <= 2.7.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.7.6; sites on affected versions should update now. Disclosed May 2024, reported by Dhabaleshwar Das.
Vulnerability Overview
The Translate Multilingual sites – TranslatePress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.7.5. This is due to missing or incorrect nonce validation on the trp_prepare_options_for_database_optimization() function. This makes it possible for unauthenticated attackers to trigger a database optimization via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
TranslatePress <= 2.7.5 carries this weakness at trp_prepare_options_for_database_optimization(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For TranslatePress the fix is 2.7.6: builds <= 2.7.5 are affected, anything from 2.7.6 onward is not.
Remediation
Update to version 2.7.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to TranslatePress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: TranslatePress 2.7.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in TranslatePress – Translate Multilingual sites with AI Translation
- 9.8CVE-2026-19632: TranslatePress – Multilingual Account Takeover
CVE-2026-19632 - 8.1CVE-2025-58592: TranslatePress <= 2.10.2 PHP Object Injection
CVE-2025-58592 - 7.3CVE-2026-78267: TranslatePress Privilege Escalation
CVE-2026-78267 - 7.2CVE-2026-76053: TranslatePress <= 3.3.3 Stored Cross-Site Scripting
CVE-2026-76053 - 7.2CVE-2026-66582: TranslatePress Stored XSS
CVE-2026-66582 - 7.2CVE-2026-75981: TranslatePress Stored XSS
CVE-2026-75981 - 7.2CVE-2026-18510: TranslatePress <= 3.2.6 Stored Cross-Site Scripting
CVE-2026-18510 - 7.2CVE-2025-30773: TranslatePress <= 2.9.6 PHP Object Injection
CVE-2025-30773
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C