Transposh WordPress Translation <= 1.0.9.1 - Missing Authorization Checks
Strategic Overview
- Status
- Patched in 1.0.9.2
- Affected Plugin
- Transposh WordPress Translation
- Affected Version
<= 1.0.9.1- CVSS
- 6.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-25810
At a glance
CVE-2022-25810 is a medium-severity Missing Authorization vulnerability in the Transposh WordPress Translation WordPress plugin, affecting versions <= 1.0.9.1. It carries a CVSS score of 6.3 (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.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 authorization bypass due to a missing capability check on several functions called via AJAX actions in versions up to, and including, 1.0.9.1. This makes it possible for authenticated attackers with subscriber-level permissions and above to perform many administrative actions such as initiating new back-ups, modifying the plugin's settings, deleting duplicates, and more.
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 Transposh WordPress Translation <= 1.0.9.1 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 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?
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: Transposh WordPress Translation 1.0.9.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- 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.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-2462: Transposh WordPress Translation Info Disclosure
CVE-2022-2462 - 4.9CVE-2022-25811: Transposh WordPress Translation SQL Injection
CVE-2022-25811 - 4.3CVE-2021-24912: Transposh WordPress Translation <= 1.0.9.1 CSRF
CVE-2021-24912
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C