CVE-2010-5266
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 · uneditedUntrusted search path vulnerability in VideoCharge Studio 2.9.0.632 allows local users to gain privileges via a Trojan horse dwmapi.dll file in the current working directory, as demonstrated by a directory that contains a .vsc file. NOTE: some of these details are obtained from third party information.
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 confidenceThis is a DLL hijacking (untrusted search path) vulnerability in VideoCharge Studio. When the application opens a .vsc file from a directory, it loads dwmapi.dll from that same directory before checking system paths. An attacker can place a malicious dwmapi.dll in a directory containing a .vsc file; when a user opens the file, the trojaned DLL executes with the application's privileges, enabling local privilege escalation.
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= 2.9.0.632CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 VideoCharge Studio installationCheck for VideoCharge Studio in the program files directory (typically C:\Program Files\VideoCharge or C:\Program Files (x86)\VideoCharge) or use registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to locate the application.Affected if VideoCharge Studio version 2.9.0.632 is installed on the system.
-
Confirm installed version numberLocate the executable (typically VideoChargeStudio.exe) and check its version properties, or query the uninstall registry entry for the version string.Affected if The installed version is exactly 2.9.0.632.
-
Check .vsc file associationVerify if .vsc files are associated with VideoCharge Studio by examining registry keys under HKCR\.vsc or by checking the application's file type associations in the Windows registry.Affected if The .vsc file extension is associated with VideoCharge Studio.
-
Test for DLL search order vulnerabilityCreate a test directory with a dummy .vsc file and a dwmapi.dll (can use Process Monitor from Sysinternals to observe DLL loading behavior when VideoCharge Studio opens the .vsc file).Affected if The application loads dwmapi.dll from the same directory as the opened .vsc file before system directories.
A user is affected if VideoCharge Studio version 2.9.0.632 is installed and configured to handle .vsc files, allowing potential DLL hijacking when those files are opened from directories containing a malicious dwmapi.dll.
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 dataUsers should avoid opening .vsc files from untrusted or shared directories. Application vendors should fix DLL loading by using fully qualified paths, manifests, or delay-loaded DLLs to prevent hijacking.
- Consultation4.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5266 — 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-2010-5266 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