B1GBB Visitenkarte.PHP Cross Site Scripting Vulnerability
BID:24698
Info
B1GBB Visitenkarte.PHP Cross Site Scripting Vulnerability
| Bugtraq ID: | 24698 |
| Class: | Input Validation Error |
| CVE: |
CVE-2007-3590 |
| Remote: | Yes |
| Local: | No |
| Published: | Jun 28 2007 12:00AM |
| Updated: | May 07 2015 05:37PM |
| Credit: | GoLd_M is credited with discovering this vulnerability. |
| Vulnerable: |
B1G b1gBB 2.24 |
| Not Vulnerable: | |
Discussion
B1GBB Visitenkarte.PHP Cross Site Scripting Vulnerability
b1gBB is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input.
Exploiting this vulnerability may allow an attacker to perform cross-site scripting attacks on unsuspecting users in the context of the affected website. As a result, the attacker may be able to steal cookie-based authentication credentials and to launch other attacks.
This issue affects b1gBB 2.24.0; other versions may also be vulnerable.
b1gBB is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input.
Exploiting this vulnerability may allow an attacker to perform cross-site scripting attacks on unsuspecting users in the context of the affected website. As a result, the attacker may be able to steal cookie-based authentication credentials and to launch other attacks.
This issue affects b1gBB 2.24.0; other versions may also be vulnerable.
Exploit / POC
B1GBB Visitenkarte.PHP Cross Site Scripting Vulnerability
To exploit this issue, an attacker must entice an unsuspecting victim into following a malicious URI.
The following proof-of-concept URI is available:
To exploit this issue, an attacker must entice an unsuspecting victim into following a malicious URI.
The following proof-of-concept URI is available:
Solution / Fix
B1GBB Visitenkarte.PHP Cross Site Scripting Vulnerability
Solution:
Currently we are not aware of any vendor fixes for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution:
Currently we are not aware of any vendor fixes for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].