CVE-2024-24810 is a high-severity (CVSS 8.2) CWE-426 vulnerability in wix. A fix is available for wix — see the affected versions and patch details below.
WiX is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-24810.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
wix.NETwixReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Summary
.be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges.
Details
If the bundle is not run as admin, the user's TEMP folder is used and not the system TEMP folder. A utility is able to monitor the user's TEMP folder for changes and drop its own DLL into the .be/<bundle>.Local folder immediately when the .be folder is created. When the burn engine elevates, the malicious DLL receives elevated privileges.
PoC
As a standard, non-admin user:
- Monitor the user's TEMP folder for changes using ReadDirectoryChangesW
- On FILE_ACTION_ADDED, check if the folder name is .be
- Create a folder in .be named after the bundle + .Local (e.g. MyInstaller.exe.Local)
- Put the malicious COMCTL32.DLL in the .Local folder following the naming used for the real DLL (e.g. MyInstaller.exe.Local/x86_microsoft.windows.common-controls_.../COMCTL32.dll)
- Do hacker things when the engine escalates and the malicious DLL is loaded
Proper naming for the path can be obtained by using GetModuleHandle("comctl32.dll") and GetModuleFileName.
Impact
DLL redirection utilizing .exe.Local Windows capability. This impacts any installer built with the WiX installer framework.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | wix | ≥ 4.0.0&&< 4.0.4 | 4.0.4dotnet add package wix --version 4.0.4 |
| .NETNuGet | wix | all versions | 3.14.0dotnet add package wix --version 3.14.0 |
Affected Products
wix toolsetfiregiantDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wix to 4.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-24810 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2024-24810 in your dependencies?
Find it across NuGet, including transitive dependencies.