Transposh WordPress Translation <= 1.0.9.6 - Unauthorized Settings Change
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Transposh WordPress Translation
- Affected Version
<= 1.0.9.6- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-2461
At a glance
CVE-2022-2461 is a medium-severity Missing Authorization vulnerability in the Transposh WordPress Translation WordPress plugin, affecting versions <= 1.0.9.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2022, reported by Julien Ahrens.
Vulnerability Overview
The Transposh WordPress Translation plugin for WordPress is vulnerable to unauthorized setting changes by unauthenticated users in versions up to, and including, 1.0.9.6. This is due to insufficient permissions checking on the 'tp_translation' AJAX action and default settings which makes it possible for unauthenticated attackers to influence the data shown on the site.
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, and no interaction from a victim user.
CWE-862: Missing Authorization
Transposh WordPress Translation <= 1.0.9.6 carries this weakness at tp_translation, and reaching it 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. No fixed build of this plugin is recorded for Transposh WordPress Translation yet, so installs running <= 1.0.9.6 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Same weakness class
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