Transposh Wordpress Translation vulnerabilities

CVE-2022-2536 [MEDIUM] CVE-2022-2536: The Transposh WordPress Translation plugin for WordPress is vulnerable to unauthorized setting chang 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 validation of settings on the 'tp_translation' AJAX action which makes it possible for unauthenticated attackers to bypass any restrictions and influence the data

CVE-2022-2462 [MEDIUM] CWE-200 CVE-2022-2462: The Transposh WordPress Translation plugin for WordPress is vulnerable to sensitive information disc The Transposh WordPress Translation plugin for WordPress is vulnerable to sensitive information disclosure to unauthenticated users in versions up to, and including, 1.0.9.6. This is due to insufficient permissions checking on the 'tp_history' AJAX action and insufficient restriction on the data returned in the response. This makes it possible for una

CVE-2022-2461 [MEDIUM] CWE-862 CVE-2022-2461: The Transposh WordPress Translation plugin for WordPress is vulnerable to unauthorized setting chang 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

CVE-2022-25811 [HIGH] CWE-89 CVE-2022-25811: The Transposh WordPress Translation WordPress plugin through 1.0.8 does not sanitise and escape the The Transposh WordPress Translation WordPress plugin through 1.0.8 does not sanitise and escape the order and orderby parameters before using them in a SQL statement, leading to a SQL injection

CVE-2022-25812 [HIGH] CWE-94 CVE-2022-25812: The Transposh WordPress Translation WordPress plugin before 1.0.8 does not validate its debug settin The Transposh WordPress Translation WordPress plugin before 1.0.8 does not validate its debug settings, which could allow allowing high privilege users such as admin to perform RCE

CVE-2022-25810 [MEDIUM] CWE-862 CVE-2022-25810: The Transposh WordPress Translation WordPress plugin through 1.0.8 exposes a couple of sensitive act The Transposh WordPress Translation WordPress plugin through 1.0.8 exposes a couple of sensitive actions such has “tp_reset” under the Utilities tab (/wp-admin/admin.php?page=tp_utils), which can be used/executed as the lowest-privileged user. Basically all Utilities functionalities are vulnerable this way, which involves resetting configurations an

CVE-2021-24910 [MEDIUM] CWE-79 CVE-2021-24910: The Transposh WordPress Translation WordPress plugin before 1.0.8 does not sanitise and escape the a The Transposh WordPress Translation WordPress plugin before 1.0.8 does not sanitise and escape the a parameter via an AJAX action (available to both unauthenticated and authenticated users when the curl library is installed) before outputting it back in the response, leading to a Reflected Cross-Site Scripting issue

CVE-2021-24911 [MEDIUM] CWE-79 CVE-2021-24911: The Transposh WordPress Translation WordPress plugin before 1.0.8 does not sanitise and escape the t The Transposh WordPress Translation WordPress plugin before 1.0.8 does not sanitise and escape the tk0 parameter from the tp_translation AJAX action, leading to Stored Cross-Site Scripting, which will trigger in the admin dashboard of the plugin. The minimum role needed to perform such attack depends on the plugin "Who can translate ?" setting.

CVE-2021-24912 [MEDIUM] CWE-79 CVE-2021-24912: The Transposh WordPress Translation WordPress plugin before 1.0.8 does not have CSRF check in its tp The Transposh WordPress Translation WordPress plugin before 1.0.8 does not have CSRF check in its tp_translation AJAX action, which could allow attackers to make authorised users add a translation. Given the lack of sanitisation in the tk0 parameter, this could lead to a Stored Cross-Site Scripting issue which will be executed in the context of a log