0day.today - Biggest Exploit Database in the World.
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn
GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Contact us
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
ModSecurity 3.0.0 - Cross-Site Scripting Vulnerability
Author
Risk
[Security Risk Medium
]0day-ID
Category
Date add
CVE
Platform
# Exploit Title: ModSecurity 3.0.0 - Cross-Site Scripting # Vendor Homepage: https://www.modsecurity.org # Software: ModSecurity # Category: Web Application Firewall # Exploit Author: Adipta Basu # Tested on: Mac OS High Sierra # CVE: N/A # Description: ModSecurity 3.0.0 has XSS via an onError attribute of an IMG element # Details: # After doing source code analysis, I found that if <img src=x onError=prompt(111)> # is passed as a parameter, a pop-up is obtained. This is because the filter flags # terms like "script","alert",etc. Moreover it also flags if there is a string placed # inside the first bracket. That is why I had to use 111. However document.cookie when # passed works fine. Reproduction Steps: - Use <img src=x onError=prompt(3)> or <img src=x onError=prompt(document.cookie)> # 0day.today [2024-11-15] #