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

> Local attackers can write to the XAMPP directory and execute code with administrative privileges due to insecure permissions.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-x73p-g67h-gmc8

## What is CVE-2022-47637?

CVE-2022-47637 is a medium-severity vulnerability in n/a, published on 12 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The installer in XAMPP through 8.1.12 allows local users to write to the C:\xampp directory. Common use cases execute files under C:\xampp with administrative privileges.

Weakness: CWE-281 (Improper Preservation of Permissions)

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

It affects 1 product.


Products: Apachefriends Xampp.

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

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

## Is CVE-2022-47637 being exploited?

There is no known exploitation of CVE-2022-47637 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-2022-29376](https://insights.sbomify.com/CVE-2022-29376/): Privilege escalation in n/a (high 8.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)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47637 is a medium-severity vulnerability in n/a, published on 12 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47637 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-47637/ (Markdown: https://insights.sbomify.com/CVE-2022-47637/index.md)
```

## Sources

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

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