Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2006-6197: Multiple XSS in b2evolution 1.8.2–1.9 beta

Published Dec 1, 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.
CVSS6.8Medium · v2
EPSS2.0%81st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
B2evolution
IdentifiersCVE-2006-6197CWE-79

Multiple cross-site scripting (XSS) vulnerabilities exist in b2evolution versions 1.8.2 through 1.9 beta. The vulnerabilities are present in several error handling pages, specifically in the handling of the app_name parameter in _404_not_found.page.php, _410_stats_gone.page.php, and _referer_spam.page.php, the baseurl parameter in _404_not_found.page.php, and the ReqURI parameter in _referer_spam.page.php. These parameters are not properly sanitized, allowing attackers to inject arbitrary web script or HTML.

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 remote attackers to execute arbitrary JavaScript or HTML in the context of the affected site, potentially leading to session hijacking, defacement, or redirection to malicious sites.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, restrict access to the affected error pages, implement web application firewall (WAF) rules to filter malicious input, and ensure user input is properly sanitized and output is encoded.

Remediation

Patch, then assume compromise.

Upgrade to a version of b2evolution where these parameters are properly sanitized and output is correctly encoded to prevent XSS. Apply any vendor-supplied patches addressing these issues.

Public exploits

Exploits

No validated public exploits yet. Hidden: 3 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
B2evolutionB2evolutionapplication
FAQ

Frequently asked questions

Is CVE-2006-6197 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2006-6197 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2006-6197?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2006-6197.
Is there a patch for CVE-2006-6197?
Upgrade to a version of b2evolution where these parameters are properly sanitized and output is correctly encoded to prevent XSS. Apply any vendor-supplied patches addressing these issues.
What products are affected by CVE-2006-6197?
B2evolution.
How severe is CVE-2006-6197?
CVE-2006-6197 has a CVSS v2 score of 6.8 (Medium) and an EPSS score of 2.0% (81st 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.