The Transposh WordPress Translation plugin for WordPress is vulnerable to unauthorized setting changes by unauthenticated users in versions up to, and including, 1.0.8.1. This is due to insufficient validation of settings on the 'tp_translation' AJAX action which makes it possible for unauthenticated attackers to bypass any restrictions and influence the data shown on the site. Please note this is a separate issue from CVE-2022-2461. Notes from the researcher: When installed Transposh comes with a set of pre-configured options, one of these is the "Who can translate" setting under the "Settings" tab. However, this option is largely ignored, if Transposh has enabled its "autotranslate" feature (it's enabled by default) and the HTTP POST parameter "sr0" is larger than 0. This is caused by a faulty validation in "wp/transposh_db.php."
| Link | Tags |
|---|---|
| https://www.wordfence.com/threat-intel/vulnerabilities/id/c774b520-9d9f-4102-8564-49673d5ae1e6 | third party advisory |
| https://www.rcesecurity.com/2022/07/WordPress-Transposh-Exploiting-a-Blind-SQL-Injection-via-XSS/ | not applicable |
| https://plugins.trac.wordpress.org/browser/transposh-translation-filter-for-wordpress/trunk/transposh.php?rev=2682425#L1989 | third party advisory exploit |
| https://packetstormsecurity.com/files/168120/wptransposh1081-authz.txt | exploit vdb entry third party advisory |
| https://www.exploitalert.com/view-details.html?id=38949 | third party advisory exploit |
| https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-2536 | third party advisory |
| https://github.com/MrTuxracer/advisories/blob/master/CVEs/CVE-2022-2536.txt | third party advisory exploit |