# CVE-2024-49360: Path traversal in Sandboxie

> An authenticated user can read other users' sandboxed files via path traversal, bypassing intended isolation boundaries.

- **Severity:** Critical 9.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2024
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-4chj-3c28-gvmp

## What is CVE-2024-49360?

CVE-2024-49360 is a critical path traversal vulnerability in sandboxie-plus Sandboxie, published on 29 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. An authenticated user (**UserA**) with no privileges is authorized to read all files created in sandbox belonging to other users in the sandbox folders `C:\Sandbox\UserB\xxx`. An authenticated attacker who can use `explorer.exe` or `cmd.exe` outside any sandbox can read other users' files in `C:\Sandbox\xxx`. By default in Windows 7+, the `C:\Users\UserA` folder is not readable by **UserB**.
All files edited or created during the sandbox processing are affected by the vulnerability. All files in C:\Users are safe. If `UserB` runs a cmd in a sandbox, he will be able to access `C:\Sandox\UserA`. In addition, if **UserB** create a folder `C:\Sandbox\UserA` with malicious ACLs, when **UserA** will user the sandbox, Sandboxie doesn't reset ACLs ! This issue has not yet been fixed. Users are advised to limit access to their systems using Sandboxie.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-49360?

It affects 1 product.


Products: Sandboxie-Plus Sandboxie.

## How do I fix CVE-2024-49360?

No fix has been published for CVE-2024-49360 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-49360 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49360 exists.

## Other vulnerabilities in sandboxie-plus Sandboxie

- [CVE-2018-18748](https://insights.sbomify.com/CVE-2018-18748/): Security feature bypass in n/a (critical 10.0)
- [CVE-2025-64721](https://insights.sbomify.com/CVE-2025-64721/): Sandboxie's Integer Overflow in SbieIniServer::RC4Crypt allows sandbox escape and SYSTEM compromise (critical 9.9)
- [CVE-2026-34458](https://insights.sbomify.com/CVE-2026-34458/): Sandboxie-Plus privilege escalation via INI CRLF injection bypassing EditAdminOnly (critical 9.3)
- [CVE-2026-34459](https://insights.sbomify.com/CVE-2026-34459/): Sandboxie-Plus sandbox escape via uninitialized memory leak and stack overflow in GetRawInputDeviceInfoSlave (high 8.8)
- [CVE-2026-34464](https://insights.sbomify.com/CVE-2026-34464/): Sandboxie-Plus NamedPipeServer OpenHandler stack overflow via unterminated server field (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49360 and fix it if it is affected.

What it is: CVE-2024-49360 is a critical path traversal vulnerability in sandboxie-plus Sandboxie, published on 29 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49360 exists.

Affected product: sandboxie-plus Sandboxie. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-49360/ (Markdown: https://insights.sbomify.com/CVE-2024-49360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49360
- OSV: https://osv.dev/vulnerability/CVE-2024-49360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-49360/
Summaries are generated and may contain mistakes; the official description above is the record.