Every CVESearch/Get API key

GHSA-259p-rvjx-ffwg

Panel::Software Customized WiX .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges

8.2 HighFix available

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/.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.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
Required

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

What each source reports

GitHub Advisories Score used8.2

Panel::Software Customized WiX .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges

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/.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.

Record
GHSA-259p-rvjx-ffwg
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-426
Updated
2026-11-02
OSV8.2

Panel::Software Customized WiX .be TEMP folder is vulnerable to DLL redirection attacks that allow the attacker to escalate privileges

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/.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.

Record
GHSA-259p-rvjx-ffwg
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-426
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
PanelSW.Custom.WiX
NuGet
before 3.15.0-a44
3.15.0-a44
PanelSW.Custom.WiX
NuGet
before 3.15.0-a44, plus listed versions
3.12.0-b1003.12.0-b453.12.0-b483.12.0-b533.12.0-b57
Show 45 moreShow less
3.12.0-b593.12.0-b603.12.0-b693.12.0-b823.12.0-b833.12.0-b843.12.0-b853.12.0-b863.12.0-b883.12.0-b893.12.0-b913.12.0-b923.12.0-b933.12.0-b993.12.0-c1013.12.0-c1043.12.0-c1053.12.0-c1063.12.0-c1073.12.0-c1083.12.0-c1103.12.0-c1113.12.0-c1123.12.0-c1133.12.0-c1143.12.0-c1153.12.0-c1163.12.0-c1173.12.0-c1213.12.0-c1233.12.0-c1243.12.0-c1263.12.0-c1273.12.0-c1293.12.0-c1303.12.0-c1353.12.0-c1503.12.0-c1563.12.0-c1583.12.0-c1613.12.0-c1623.12.0-c1653.12.0-c1663.12.0-c1673.12.0-c176
3.15.0-a44

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

GHSA-259p-rvjx-ffwg is a high vulnerability (CVSS 8.2) in PanelSW.Custom.WiX, published February 8, 2024. No source lists public exploit code. Fixed in PanelSW.Custom.WiX 3.15.0-a44.

References

This page doesn't list everything

Left out here: 11 versions. The JSON record has them.

MoveEnter Open