Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2006-0361: XSS in Bit 5 Blog 8.01 addcomment.php

Published Jan 22, 2006 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS2.1%82nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Bit 5 Blog
IdentifiersCVE-2006-0361CWE-79

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

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.

VendorProductType
Bit 5 BlogBit 5 Blogapplication
FAQ

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.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.