Transposh WordPress Translation versions 22.214.171.124 and below have an ajax action called “tp_history” which is intended to return data about who has translated a text given by the “token” parameter. However, the plugin also returns the user’s login name as part of the “user_login” attribute. Successful exploits can allow an unauthenticated attacker to leak the WordPress username of translators. If an anonymous user submitted the translation, then the user’s IP address is returned.
advisories | CVE-2022-2462
RCE Security Advisory
1. ADVISORY INFORMATION
Product: Transposh WordPress Translation
Vendor URL: https://wordpress.org/plugins/transposh-translation-filter-for-wordpress/
Type: Exposure of Sensitive Information to an Unauthorized Actor [CWE-200]
Date found: 2022-07-13
Date published: 2022-07-22
CVSSv3 Score: 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
This vulnerability was discovered and researched by Julien Ahrens from
3. VERSIONS AFFECTED
Transposh WordPress Translation 126.96.36.199 and below
Transposh translation filter for WordPress offers a unique approach to blog
translation. It allows your blog to combine automatic translation with human
translation aided by your users with an easy to use in-context interface.
(from the vendor's homepage)
5. VULNERABILITY DETAILS
Transposh offers an ajax action called "tp_history" which is intended to return
data about who has translated a text given by the "token" parameter. However, the
plugin also returns the user's login name as part of the "user_login" attribute.
Successful exploits can allow an unauthenticated attacker to leak the WordPress
username of translators. If an anonymous user submitted the translation, then the
user's IP address is returned.
6. PROOF OF CONCEPT
The following Proof-of-Concept returns the information of the translated text
POST /wp-admin/admin-ajax.php HTTP/1.1
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
None. Remove the plugin to prevent exploitation.
8. REPORT TIMELINE
2022-07-13: Discovery of the vulnerability
2022-07-13: CVE requested from WPScan (CNA)
2022-07-18: No response from WPScan
2022-07-18: CVE requested from Wordfence (CNA) instead
2022-07-18: Sent note to vendor
2022-07-18: Wordfence assigns CVE-2022-2462
2022-07-20: Vendor states that there is no update planned so far
2022-07-22: Public disclosure