How severe is GHSA-259p-rvjx-ffwg?

GHSA-259p-rvjx-ffwg has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-259p-rvjx-ffwg?

GHSA-259p-rvjx-ffwg affects the following packages: PanelSW.Custom.WiX (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-259p-rvjx-ffwg?

Update PanelSW.Custom.WiX to 3.15.0-a44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-259p-rvjx-ffwg is resolved across your whole dependency graph.

How do I detect GHSA-259p-rvjx-ffwg in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for PanelSW.Custom.WiX. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-259p-rvjx-ffwg if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-259p-rvjx-ffwg?

O3 pinpoints whether GHSA-259p-rvjx-ffwg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-259p-rvjx-ffwg actively exploited in the wild?

No public exploit code has been indexed for GHSA-259p-rvjx-ffwg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-259p-rvjx-ffwg published, and has it been updated?

GHSA-259p-rvjx-ffwg was published on February 8, 2024 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-259p-rvjx-ffwg

HIGH

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

Published

Feb 8, 2024

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

.NETPanelSW.Custom.WiX

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`PanelSW.Custom.WiX`	all versions	3.15.0-a44

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for PanelSW.Custom.WiX. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update PanelSW.Custom.WiX to 3.15.0-a44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-259p-rvjx-ffwg 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.
How O3 protects you
O3 pinpoints whether GHSA-259p-rvjx-ffwg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-259p-rvjx-ffwg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# 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 1. On FILE_ACTION_ADDED

O3 Security · Impact-Aware SCA

Is GHSA-259p-rvjx-ffwg in your dependencies?

O3 detects GHSA-259p-rvjx-ffwg across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works