Strategic Overview
- Status
- Patched in 1.0.4
- Affected Plugin
- My WP Translate
- Affected Version
< 1.0.4- CVSS
- 8.0High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2017-18569
At a glance
CVE-2017-18569 is a high-severity Missing Authorization vulnerability in the My WP Translate WordPress plugin, affecting versions < 1.0.4. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.0.4; sites on affected versions should update now. Disclosed October 2017.
Vulnerability Overview
The My WP Translate plugin for WordPress is vulnerable to an authorization bypass weakness in versions up to, and including, 1.0.3. This is due to missing capability checks and nonce validation on the following functions: ajax_translation_panel(), ajax_save_translation(), ajax_add_plugin(), ajax_remove_plugin(), ajax_save_state(), ajax_import_strings(), and ajax_update_export_code(). This makes it possible for low-privileged authenticated attackers to perform a wide variety of actions such as adding or removing plugins. This can also be exploited via Cross-Site Request Forgery.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
My WP Translate < 1.0.4 carries this weakness at ajax_translation_panel(), 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. For My WP Translate the fix is 1.0.4: builds < 1.0.4 are affected, anything from 1.0.4 onward is not.
Remediation
Update to version 1.0.4, 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: My WP Translate 1.0.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in My WP Translate
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C