# Malicious directory junction can cause WiX RemoveFoldersEx to possibly delete elevated files Advisory record · `GHSA-jx4p-m4wm-vvjg` - **Identifiers:** `GHSA-jx4p-m4wm-vvjg` · `CVE-2024-29188` - **State:** Confirmed - **Severity:** CVSS 7.8 High - **Critical:** No - **Weakness (CWE):** [CWE-59](https://cwe.mitre.org/data/definitions/59.html) - **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) - **Published:** 25 Mar 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 25 Mar 2024, 19:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `wix` (NuGet): affected `<3.14.1 || >=4.0.0, <4.0.5`; fixed in `3.14.1`, `4.0.5` - `WixToolset.Util.wixext` (NuGet): affected `<4.0.5`; fixed in `4.0.5` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The WiX Toolset packages wix (versions below 3.14.1, and 4.0.0 up to but not including 4.0.5) and WixToolset.Util.wixext (versions below 4.0.5) are affected. A standard user who can write to a per-user folder that a per-machine installer is told to remove with RemoveFolderEx can create a directory junction there pointing to a protected directory. When an administrator runs the installer, the protected target can be deleted. Upgrade wix to 3.14.1 or 4.0.5, and WixToolset.Util.wixext to 4.0.5. Written 9 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0024, the 15th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 15:21 UTC: First seen by agentprime - 31 Oct 2026, 15:21 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jx4p-m4wm-vvjg) ## Sources - [GitHub Advisory Database: GHSA-jx4p-m4wm-vvjg](https://github.com/advisories/GHSA-jx4p-m4wm-vvjg) - [OSV: GHSA-jx4p-m4wm-vvjg](https://osv.dev/vulnerability/GHSA-jx4p-m4wm-vvjg) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .