CVE-2006-0361: XSS in Bit 5 Blog 8.01 addcomment.php
- Vendor
- Bit 5 Blog
A cross-site scripting (XSS) vulnerability exists in Bit 5 Blog version 8.01, specifically in the addcomment.php script. The vulnerability allows remote attackers to inject arbitrary web script or HTML by submitting a comment containing a <a> tag with a javascript URI. The input sanitization strips most tags but fails to remove <a> tags, enabling the XSS vector.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows attackers to execute arbitrary JavaScript in the context of users viewing the affected blog, potentially leading to session hijacking, credential theft, or other attacks leveraging the victim's browser session.
Mitigation
If you can’t patch tonight, do this now.
As an immediate mitigation, disable or restrict comment functionality, or implement server-side filtering to remove or encode <a> tags and javascript URIs in user-submitted comments until a proper patch is applied.
Remediation
Patch, then assume compromise.
Update the input sanitization logic in addcomment.php to properly filter or encode <a> tags and their attributes, especially disallowing javascript URIs. Alternatively, use a well-maintained library for HTML sanitization that is resistant to XSS vectors.
Exploits
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2006-0361 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2006-0361 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2006-0361?
- Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2006-0361.
- Is there a patch for CVE-2006-0361?
- Update the input sanitization logic in addcomment.php to properly filter or encode <a> tags and their attributes, especially disallowing javascript URIs. Alternatively, use a well-maintained library for HTML sanitization that is resistant to XSS vectors.
- What products are affected by CVE-2006-0361?
- Bit 5 Blog.
- How severe is CVE-2006-0361?
- CVE-2006-0361 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 2.1% (82nd percentile) as of Oct 16, 2026.
Recent activity
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.