BLOG:CMS ID Parameter Cross-Site Scripting Vulnerability
BID:19111
Info
BLOG:CMS ID Parameter Cross-Site Scripting Vulnerability
| Bugtraq ID: | 19111 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 17 2006 12:00AM |
| Updated: | Jul 24 2006 06:22PM |
| Credit: | David Vieira-Kurz is credited with the discovery of this vulnerability. |
| Vulnerable: |
BLOG:CMS BLOG:CMS 4.0 j |
| Not Vulnerable: | |
Discussion
BLOG:CMS ID Parameter Cross-Site Scripting Vulnerability
BLOG:CMS is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input.
An attacker may leverage this issue to have arbitrary script code execute in the browser of an unsuspecting user in the context of the affected site. This may help the attacker steal cookie-based authentication credentials and launch other attacks.
Version 4.0.0j of BLOG:CMS is vulnerable to this issue; prior versions may also be affected.
BLOG:CMS is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input.
An attacker may leverage this issue to have arbitrary script code execute in the browser of an unsuspecting user in the context of the affected site. This may help the attacker steal cookie-based authentication credentials and launch other attacks.
Version 4.0.0j of BLOG:CMS is vulnerable to this issue; prior versions may also be affected.
Exploit / POC
BLOG:CMS ID Parameter Cross-Site Scripting Vulnerability
Attackers can exploit this issue via a web client.
Attackers can exploit this issue via a web client.
Solution / Fix
BLOG:CMS ID Parameter 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 if you are aware of more recent information, please mail us at: [email protected]:[email protected].
Solution:
Currently we are not aware of any vendor-supplied patches 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]:[email protected].