CVE-2007-3296
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe ThunderServer.webThunder.1 ActiveX control in xunlei Web Thunderbolt 1.7.3.109 allows remote attackers to download arbitrary files and conduct other unauthorized actions by invoking dangerous methods.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe ThunderServer.webThunder.1 ActiveX control in xunlei Web Thunderbolt 1.7.3.109 contains dangerous methods that can be invoked by remote attackers to download arbitrary files onto vulnerable systems and perform unauthorized actions. This is a classic ActiveX vulnerability where the control exposes unsafe functionality without proper validation or authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.7.3.109CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Xunlei Web Thunderbolt installationCheck for Xunlei Web Thunderbolt in installed programs via Control Panel > Programs and Features, or check the installation directory (commonly C:\Program Files\Xunlei\WebThunder or similar paths).Affected if Xunlei Web Thunderbolt version 1.7.3.109 is installed on the system.
-
Confirm ActiveX control registrationOpen Command Prompt and run: reg query 'HKLM\SOFTWARE\Classes\ThunderServer.webThunder.1' to check if the ActiveX control is registered in the Windows registry.Affected if The registry key ThunderServer.webThunder.1 exists, indicating the vulnerable ActiveX control is registered.
-
Check if control is allowed to run in Internet ExplorerIn Internet Explorer, go to Internet Options > Security > Custom Level > ActiveX controls and plugins, or check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved for the CLSID of this control.Affected if The ActiveX control is not set to disabled or the killbit is not set.
-
Identify the CLSID for additional verificationQuery the registry at HKLM\SOFTWARE\Classes\ThunderServer.webThunder.1\CLSID to retrieve the control's CLSID, then verify whether the killbit is set at HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{CLSID} or in the registry path used for killbit enforcement.Affected if The control's CLSID exists without an accompanying killbit entry that would block its execution.
A system is affected if Xunlei Web Thunderbolt 1.7.3.109 is installed and the ThunderServer.webThunder.1 ActiveX control is registered and not disabled via killbit or browser settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the vulnerable ThunderServer.webThunder.1 ActiveX control. Deploy the Microsoft killbit for this control if a vendor patch is unavailable, or upgrade to a patched version of the software if one exists.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3296 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-3296 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data