BrowserCRM vulnerable for XSS

Risk: Low
Local: Yes
Remote: Yes

CVSS Base Score: 4.3/10
Impact Subscore: 2.9/10
Exploitability Subscore: 8.6/10
Exploit range: Remote
Attack complexity: Medium
Authentication: No required
Confidentiality impact: None
Integrity impact: Partial
Availability impact: None

Inputs in the BrowserCRM is not properly sanitized, and XSS is possible in a lot of the systems input fields and url parameters. Some fields have been filtered in a basic form, so that simple scripting like "<script>alert('XSS')</script>" is not possible. Howevere, since the filtering is not based on white listing you can conduct successful XSS attacks with code like "<IMG SRC=javascript:alert(String.fromCharCode(88,83,83))>". PoC: http://www.SITE.example/modules/Search/results.php?query=%3CIMG+SRC%3Dja vascript%3Aalert%28String.fromCharCode%2888%2C83%2C83%29%29%3E Vendors site: Please credit to: Preben Nyl?kken

Vote for this issue:


Thanks for you vote!


Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2018,


Back to Top