Transposh WordPress Translation <= 1.0.9.1 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.0.9.2
- Affected Plugin
- Transposh WordPress Translation
- Affected Version
<= 1.0.9.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-24912
At a glance
CVE-2021-24912 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Transposh WordPress Translation WordPress plugin, affecting versions <= 1.0.9.1. 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 1.0.9.2; sites on affected versions should update now. Disclosed July 2022, reported by Julien Ahrens.
Vulnerability Overview
The Transposh WordPress Translation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.9.1. This is due to missing nonce validation on several AJAX action function. This makes it possible for unauthenticated attackers to performa variety of actions such as initiating a back-up, changing the plugin's settings, and deleting duplicates via forged requests 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)
Reaching this weakness in Transposh WordPress Translation <= 1.0.9.1 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 Transposh WordPress Translation the fix is 1.0.9.2: builds <= 1.0.9.1 are affected, anything from 1.0.9.2 onward is not.
Remediation
Update to version 1.0.9.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Transposh WordPress Translation: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Transposh WordPress Translation 1.0.9.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Transposh WordPress Translation
- 7.2CVE-2022-25812: Transposh WordPress Translation <= 1.0.9.1 RCE
CVE-2022-25812 - 6.5CVE-2021-24911: Transposh WordPress Translation <= 1.0.7 Stored XSS
CVE-2021-24911 - 6.3CVE-2022-25810: Transposh WordPress… Missing Authorization Checks
CVE-2022-25810 - 6.1CVE-2021-24910: Transposh WordPress Translation <= 1.0.7 Reflected XSS
CVE-2021-24910 - 5.3CVE-2022-2536: Transposh WordPress Translation Authorization Bypass
CVE-2022-2536 - 5.3CVE-2022-2461: Transposh WordPress… Unauthorized Settings Change
CVE-2022-2461 - 5.3CVE-2022-2462: Transposh WordPress Translation Info Disclosure
CVE-2022-2462 - 4.9CVE-2022-25811: Transposh WordPress Translation SQL Injection
CVE-2022-25811
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C