# CVE-2025-47422: Privilege escalation in n/a

> A low-privileged attacker can achieve arbitrary SYSTEM code execution by placing a malicious binary in a writable folder when Advanced Installer runs as SYSTEM.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 24 Jul 2025
- **Also known as:** GHSA-jxf5-j9w5-328x

## What is CVE-2025-47422?

CVE-2025-47422 is a high-severity vulnerability in n/a, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Advanced Installer before 22.6 has an uncontrolled search path element local privilege escalation vulnerability. When running as SYSTEM in certain configurations, Advanced Installer looks in standard-user writable locations for non-existent binaries and executes them as SYSTEM. A low-privileged attacker can place a malicious binary in a targeted folder; when the installer is executed, the attacker achieves arbitrary SYSTEM code execution.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-47422?


## How do I fix CVE-2025-47422?

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

## Is CVE-2025-47422 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47422 and fix it if it is affected.

What it is: CVE-2025-47422 is a high-severity vulnerability in n/a, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47422 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-2025-47422/ (Markdown: https://insights.sbomify.com/CVE-2025-47422/index.md)
```

## Sources

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

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