Transposh WordPress Translation <= 1.0.9.1 - Remote Code Execution
Strategic Overview
- Status
- Patched in 1.0.9.2
- Affected Plugin
- Transposh WordPress Translation
- Affected Version
<= 1.0.9.1- CVSS
- 7.2High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2022-25812
At a glance
CVE-2022-25812 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Transposh WordPress Translation WordPress plugin, affecting versions <= 1.0.9.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). 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 remote code execution in versions up to, and including, 1.0.9.1. This is due to insufficient extension validation on the log file that can be created via the plugin. This makes it possible for authenticated attackers with administrative level permissions and above to set the log file extension to .php and then update a setting to log PHP executable code to that file which can be used to achieve remote code execution.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Transposh WordPress Translation <= 1.0.9.1 takes a caller who can reach the endpoint. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created 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
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Transposh WordPress Translation
- 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 - 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