Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2009-3747: XSS in TBmnetCMS 1.0 index.php

Published Oct 22, 2009 · 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
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Tbmnet
IdentifiersCVE-2009-3747CWE-79 · Improper Neutralization of Input…

A cross-site scripting (XSS) vulnerability exists in TBmnetCMS 1.0, specifically in index.php, where the 'content' parameter is not properly sanitized, allowing remote 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 attackers to execute arbitrary JavaScript in the context of the victim's browser, potentially leading to session hijacking, credential theft, or defacement.

Mitigation

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

Implement input validation and output encoding for the 'content' parameter. Employ web application firewalls (WAFs) to detect and block XSS payloads as an interim measure.

Remediation

Patch, then assume compromise.

Upgrade to a version of TBmnetCMS that properly sanitizes user input in the 'content' parameter, or apply a patch that escapes or filters HTML/JavaScript content.

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
TbmnetTbmnetcmsapplication
FAQ

Frequently asked questions

Is CVE-2009-3747 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-3747 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-3747?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2009-3747.
Is there a patch for CVE-2009-3747?
Upgrade to a version of TBmnetCMS that properly sanitizes user input in the 'content' parameter, or apply a patch that escapes or filters HTML/JavaScript content.
What products are affected by CVE-2009-3747?
Tbmnetcms.
How severe is CVE-2009-3747?
CVE-2009-3747 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 1.5% (75th 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.