CVE-2024-24810
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.24 % · percentile 14.54 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
WiX toolset lets developers create installers for Windows Installer, the Windows installation engine. The .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges. This impacts any installer built with the WiX installer framework. This issue has been patched in version 4.0.4.
Read the publisher's advisoryWiX toolset lets developers create installers for Windows Installer, the Windows installation engine. The .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges. This impacts any installer built with the WiX installer framework. This issue has been patched in version 4.0.4.
Read the publisher's advisoryWiX toolset lets developers create installers for Windows Installer, the Windows installation engine. The .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges. This impacts any installer built with the WiX installer framework. This issue has been patched in version 4.0.4.
Read the publisher's advisory### 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: 1. Monitor the user's TEMP folder for changes using ReadDirectoryChangesW 2. On FILE_ACTION_ADDED, check if the folder name is .be 3. Create a folder in .be named after the bundle + .Local (e.g. MyInstaller.exe.Local) 4. 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) 5. 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.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.24 % · percentile 14.54 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2024-24810 · 15 Nov 2026 14:45:34 UTC
CVE-2024-24810 · 14 Nov 2026 16:37:01 UTC
CVE-2024-24810 · 13 Nov 2026 19:59:34 UTC
CVE-2024-24810 · 12 Nov 2026 18:18:51 UTC
CVE-2024-24810 · 10 Nov 2026 20:24:10 UTC
CVE-2024-24810 · 09 Nov 2026 21:04:24 UTC
CVE-2024-24810 · 08 Nov 2026 15:12:21 UTC
CVE-2024-24810 · 07 Nov 2026 16:07:52 UTC
CVE-2024-24810 · 06 Nov 2026 19:10:17 UTC
CVE-2024-24810 · 05 Nov 2026 22:49:22 UTC
CVE-2024-24810 · 05 Nov 2026 02:54:06 UTC
CVE-2024-24810 · 03 Nov 2026 16:59:18 UTC
CVE-2024-24810 · 02 Nov 2026 23:59:04 UTC
CVE-2024-24810 · 01 Nov 2026 23:58:58 UTC
CVE-2024-24810 · 01 Nov 2026 03:04:52 UTC
CVE-2024-24810 · 31 Oct 2026 01:52:30 UTC
CVE-2024-24810 · 29 Oct 2026 18:29:26 UTC
CVE-2024-24810 · 28 Oct 2026 19:55:37 UTC
CVE-2024-24810 · 27 Oct 2026 15:46:19 UTC
CVE-2024-24810 · 27 Oct 2026 00:23:05 UTC
CVE-2024-24810 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
euvd · EUVD-2024-0564 · Published
nvd · CVE-2024-24810 · Published
osv · GHSA-7wh2-wxc7-9ph5 · Published
cve-program · CVE-2024-24810 · Published