CVE-2006-0800: XSS
Interpretation conflict in PostNuke 0.761 and earlier allows remote attackers to conduct cross-site scripting (XSS) attacks via HTML tags with a trailing "<" character, which is interpreted as a ">" character by some web browsers but bypasses the blacklist protection in (1) the pnVarCleanFromInput function in pnAPI.php, (2) the pnSecureInput function in pnAntiCracker.php, and (3) the htmltext parameter in an edituser operation to user.php.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2006-0800?
CVE-2006-0800 is classified as a medium severity vulnerability due to its potential for allowing cross-site scripting attacks.
How do I fix CVE-2006-0800?
To fix CVE-2006-0800, upgrade to a fixed version of PostNuke that addresses this vulnerability, specifically versions later than 0.761.
Which versions of PostNuke are affected by CVE-2006-0800?
CVE-2006-0800 affects PostNuke versions 0.71, 0.63, 0.64, 0.703, 0.761, and several 0.76 release candidates and earlier.
What kind of attacks can be executed using CVE-2006-0800?
CVE-2006-0800 allows attackers to perform cross-site scripting (XSS) attacks, potentially leading to session hijacking and data manipulation.
Is user input protection affected by CVE-2006-0800?
Yes, CVE-2006-0800 exploits a flaw in user input sanitation, allowing HTML tags with a trailing '<' to bypass blacklist protections.