0day.today - Biggest Exploit Database in the World.
Things you should know about 0day.today:
Administration of this site uses the official contacts. Beware of impostors!
- 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!
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!
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
WeBid 1.0.2 presistent XSS via SQL Injection
# Exploit Title: presistent XSS through SQLi WeBid 1.0.2 # Google Dork: "powered by WeBid" # Author: Saif El-Sherei # Software Link: http://sourceforge.net/projects/simpleauction/ # Version: 1.0.2 # Tested on: Firefox 4, XAMPP Info: Open source php/mysql fully featured auction script. Perfect for those who want to start their own auction site. Details: an attacker could inject malicous HTML/JS through a SQL injection flow in the adsearch.php. the SQl injection flaw exist in the "maxprice" field (see POC I). the SQL injection attack cannot be elevated, so we leverage the SQL injection to trigger an error that would write our malicious HTML/JS to the error log. the XSS attack happens when the admin or any user capable of viewing the error log from the ACP. POC I (SQL injection): '0') ----> this will trigger the error '0') OR (1)=(1 ------> will not trigger error POC II (XSS through SQLi): '0') <script>alert('XSS');</script> Time Line: 15-06-2011 Vulnerability discovered 15-06-2011 Vendor notified 17-06-2011 No response from vendor, public disclosure # 0day.today [2024-11-15] #