MyWeight Multiple Cross Site Scripting Vulnerabilities
BID:43488
Info
MyWeight Multiple Cross Site Scripting Vulnerabilities
| Bugtraq ID: | 43488 |
| Class: | Input Validation Error |
| CVE: |
CVE-2009-3512 |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 20 2009 12:00AM |
| Updated: | Jul 20 2009 12:00AM |
| Credit: | Moudi |
| Vulnerable: |
phplemon MyWeight 1.0 |
| Not Vulnerable: | |
Discussion
MyWeight Multiple Cross Site Scripting Vulnerabilities
MyWeight is prone to multiple cross-site scripting vulnerabilities because it fails to sufficiently sanitize user-supplied data.
An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and to launch other attacks.
phplemon MyWeight 1.0 is vulnerable; others versions may be affected.
MyWeight is prone to multiple cross-site scripting vulnerabilities because it fails to sufficiently sanitize user-supplied data.
An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and to launch other attacks.
phplemon MyWeight 1.0 is vulnerable; others versions may be affected.
Exploit / POC
MyWeight Multiple Cross Site Scripting Vulnerabilities
To exploit these issues, an attacker must entice an unsuspecting user to visit a malicious URI.
The following example URIs are available:
To exploit these issues, an attacker must entice an unsuspecting user to visit a malicious URI.
The following example URIs are available:
Solution / Fix
MyWeight Multiple Cross Site Scripting Vulnerabilities
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].