WPML WordPress Plugin Vulnerabilities Expose 400,000 Websites

The Developers of WPML Have Released an Update to Address Several Security Issues that Can be Exploited to Access Website Databases, Delete Content and Perform Administrative Actions. WPML is a Premium Plugin Designed for Running Fully Multilingual Websites with WordPress. The Official WPML Website Shows that, the Application is Installed on More than 400,000 Commercial Sites. A Total of 4 Vulnerabilities Have been Identified and Reported by Jouko Pynnonen, the CEO of Finland-Based IT Company, Klikki Oy. According to the Expert, the Most Serious Flaw is an SQL Injection that Can be Exploited by an Unauthenticated Attacker to Read the Contents of an Affected Website’s Database, including Password Hashes and Other User Details. “When WPML processed a HTTP POST request containing the parameter ‘action=wp-link-ajax’, the current language is determined by parsing the HTTP referer. The parsed language code is not checked for validity, nor SQL-escaped”, Pynnonen Explained in an Advisory. “By sending a carefully crafted referer value with the mentioned POST request parameter, an attacker can perform SQL queries on arbitrary tables and retrieve their results.”


Another Serious Issue Allows the Removal of Content from Websites, including Pages, Posts and Menus. The Flaw is Caused by the Lack of Access Control in the “Menu Sync” Functionality, which Allows Administrators to Keep WordPress Menus Consistent across Different Languages, Pynnonen Said. The Researcher has also Identified a Reflected Cross-Site Scripting (XSS) Vulnerability in the WPML “Reminder Popup” Code. An Attacker Can Leverage the Bug to Execute Arbitrary JavaScript in the Targeted User’s Browser. The Last Security Hole Identified by Pynnonen, Can be Exploited by an Unauthenticated Attacker to Bypass the WPML nonce Check and Perform any of the Approximately 50 Ajax Functions Designed to be Used by Website Admins. “The administrative ajax functions are protected with nonces to prevent unauthorized use. If the nonce check failed with $_REQUEST values, there was a secondary check that also had to fail before the request was denied”, the Expert Explained. “The problem is the mixed use of $_REQUEST and $_GET. If the above check succeeds, subsequent code again uses $_REQUEST instead of $_GET to determine the ajax action to perform. If the attacker has a valid nonce generated by the target WordPress site - any plug-in or the core system - then they can pass the above check."


"They can then define a different Ajax action in POST parameters to perform administrative functions without authentication”, he Added. The Vulnerabilities were Reported on March 2 and they were Addressed by OnTheGoSystems Last Week with the Release of WPML 3.1.9. However, since the Update Caused WPML to Decode Non-English URLs Incorrectly, Version 3.1.9.1 was also Released to Address this Functionality Bug. “We take the security of our clients very seriously, so as soon as we noticed these possible exploits, we set to work on a version which fixes them”, WPML Developers Wrote in a Blog Post. In September 2014, Pynnonen Identified a Critical XSS Vulnerability in WordPress itself. The Vulnerability Could Have been Exploited by a Remote Attacker to Compromise Websites with the Aid of Specially Crafted Comments.




Info Sources:

http://klikki.fi/adv/wpml.html

http://wpml.org/2015/03/wpml-security-update-bug-and-fix