# CVE-2022-29376: Privilege escalation in n/a

> Attackers can execute arbitrary code by overwriting binaries in the insecurely permissioned XAMPP installation directory on Windows.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2022
- **Updated:** 15 Aug 2025
- **Also known as:** GHSA-4q7h-5rhf-q8ch

## What is CVE-2022-29376?

CVE-2022-29376 is a high-severity vulnerability in n/a, published on 23 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Xampp for Windows v8.1.4 and below was discovered to contain insecure permissions for its install directory, allowing attackers to execute arbitrary code via overwriting binaries located in the directory.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-29376?

It affects 1 product.


Products: Apachefriends Xampp.

## How do I fix CVE-2022-29376?

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

## Is CVE-2022-29376 being exploited?

There is no known exploitation of CVE-2022-29376 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-8923](https://insights.sbomify.com/CVE-2019-8923/): SQL injection in n/a (critical 9.8)
- [CVE-2020-11107](https://insights.sbomify.com/CVE-2020-11107/): Privilege escalation in n/a (high 8.8)
- [CVE-2009-0919](https://insights.sbomify.com/CVE-2009-0919/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2024-0338](https://insights.sbomify.com/CVE-2024-0338/): Buffer Overflow Vulnerability in XAMPP (high 7.3)
- [CVE-2008-6498](https://insights.sbomify.com/CVE-2008-6498/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29376 and fix it if it is affected.

What it is: CVE-2022-29376 is a high-severity vulnerability in n/a, published on 23 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29376 in the wild and no public exploit code.

Affected product: n/a. 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-2022-29376/ (Markdown: https://insights.sbomify.com/CVE-2022-29376/index.md)
```

## Sources

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

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