vBulletin newreply.php Cross-Site Scripting Vulnerability
BID:10612
Info
vBulletin newreply.php Cross-Site Scripting Vulnerability
| Bugtraq ID: | 10612 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Jun 26 2004 12:00AM |
| Updated: | Jun 26 2004 12:00AM |
| Credit: | Discovery of this issue is credited to Cheng Peng Su. |
| Vulnerable: |
VBulletin VBulletin 3.0.1 VBulletin VBulletin 3.0 Gamma VBulletin VBulletin 3.0 beta 7 VBulletin VBulletin 3.0 beta 6 VBulletin VBulletin 3.0 beta 5 VBulletin VBulletin 3.0 beta 4 VBulletin VBulletin 3.0 beta 3 VBulletin VBulletin 3.0 beta 2 |
| Not Vulnerable: | |
Discussion
vBulletin newreply.php Cross-Site Scripting Vulnerability
vBulletin is reportedly affected by a cross-site scripting vulnerability in the newreply.php script. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
An attacker may exploit this issue to have malicious HTML or script code executed in the browser of an unsuspecting user and within the context of a visited web site. This may potentially lead to theft of cookie based authentication credentials, other attacks are also possible.
vBulletin is reportedly affected by a cross-site scripting vulnerability in the newreply.php script. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
An attacker may exploit this issue to have malicious HTML or script code executed in the browser of an unsuspecting user and within the context of a visited web site. This may potentially lead to theft of cookie based authentication credentials, other attacks are also possible.
Exploit / POC
vBulletin newreply.php Cross-Site Scripting Vulnerability
No exploit is required to leverage this issue.
No exploit is required to leverage this issue.
Solution / Fix
vBulletin newreply.php Cross-Site Scripting Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.