efd633079a
19 changes to exploits/shellcodes WordPress Core - 'load-scripts.php' Denial of Service Sync Breeze Enterprise 10.0.28 - Remote Buffer Overflow (PoC) Claymore Dual GPU Miner 10.5 - Format String Apport/ABRT - 'chroot' Local Privilege Escalation (Metasploit) MalwareFox AntiMalware 2.74.0.150 - Privilege Escalation BOCHS 2.6-5 - Buffer Overflow Windows - 'EternalRomance'/'EternalSynergy'/'EternalChampion' SMB Remote Code Execution (Metasploit) (MS17-010) Wonder CMS 2.3.1 - Unrestricted File Upload Wonder CMS 2.3.1 - 'Host' Header Injection Matrimonial Website Script 2.1.6 - 'uid' SQL Injection NixCMS 1.0 - 'category_id' SQL Injection Online Voting System - Authentication Bypass Joomla! Component Zh BaiduMap 3.0.0.1 - SQL Injection Joomla! Component Zh YandexMap 6.2.1.0 - 'id' SQL Injection Joomla! Component Zh GoogleMap 8.4.0.0 - SQL Injection Joomla! Component jLike 1.0 - Information Leak Joomla! Component JSP Tickets 1.1 - SQL Injection Student Profile Management System Script 2.0.6 - Authentication Bypass Netis WF2419 Router - Cross-Site Scripting Linux/x64 - Bind TCP (4444/TCP) Shell (/bin/sh) + Password (1234567) Shellcode (136 bytes)
28 lines
No EOL
903 B
Text
28 lines
No EOL
903 B
Text
# Exploit Title: Wonder CMS 2.3.1 Host Header Injection
|
|
# Date: 30-01-2018
|
|
# Exploit Author: Samrat Das
|
|
# Contact: http://twitter.com/Samrat_Das93
|
|
# Website: https://securitywarrior9.blogspot.in/
|
|
# Vendor Homepage: https://www.wondercms.com/
|
|
# Version: 2.3.1
|
|
# CVE : CVE-2017-14523
|
|
# Category: Webapp CMS
|
|
|
|
1. Description
|
|
|
|
The application allows illegitimate host header manipulation and leads to aribtary web page re-direction. This can also lead to severe attacks such as password reset or web cache poisoning
|
|
|
|
|
|
|
|
2. Proof of Concept
|
|
|
|
Intercept any web request of cms using a proxy tool.
|
|
Change the http host header to:
|
|
POST / HTTP/1.1
|
|
Host: google.com
|
|
|
|
You can observe the page being re-directed and the Location header changed in response to: http://www.google.com/
|
|
|
|
3. Solution:
|
|
|
|
To Mitigate host header injections allows only a whitelist of allowed hostnames. |