Get in touch

Transposh <= 1.0.8.1 “save_transposh” Missing Logfile Extension Check Leading to Code Injection

Jul 22, 2022 · By Julien Ahrens

ADVISORY INFORMATION

CREDITS

This vulnerability was discovered and researched by Julien Ahrens from RCE Security.

VERSIONS AFFECTED

Transposh WordPress Translation 1.0.8.1 and below

INTRODUCTION

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)

VULNERABILITY DETAILS

The plugin’s “save_transposh” action available at “/wp-admin/admin.php?page=tp_advanced” does not properly validate the “Log file name” allowing an attacker with the “Administrator” role to specify a .php file as the log destination.

Since the log file is stored directly within the “/wp-admin” directory, executing arbitrary PHP code is possible by simply sending a crafted request that gets logged.

Successful exploits can allow the attacker to compromise the entire WordPress installation. This is specifically relevant in multi-site installations.

PROOF OF CONCEPT

  1. Go to /wp-admin/admin.php?page=tp_advanced and “Enable debugging” by pointing it to a filename with a .php extension.
  2. Set the “Level of logging” to “Debug”
  3. Saving the settings
  4. Submit a payload like <?php phpinfo();?> to any of Transposh’s functionalities.
  5. Go to /wp-admin/[your-filename.php] to trigger the code injection

SOLUTION

None. Remove the plugin to prevent exploitation.

REPORT TIMELINE

  • 2022-02-21: Discovery of the vulnerability
  • 2022-02-21: Contacted the vendor via email
  • 2022-02-21: Vendor response
  • 2022-02-22: CVE requested from WPScan (CNA)
  • 2022-02-23: WPScan assigns CVE-2022-25812
  • 2022-05-22: Sent request for status update on the fix
  • 2022-05-24: Vendor states that there is no update planned so far
  • 2022-07-22: Public disclosure

REFERENCES

None