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

> Local attackers can escalate privileges to SYSTEM by exploiting an unquoted service path in the memoQ Auto Update Service.

- **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:** 29 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-r6ww-7hxw-68c6

## What is CVE-2025-60320?

CVE-2025-60320 is a medium-severity vulnerability in n/a, published on 29 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

memoQ 10.1.13.ef1b2b52aae and earlier contains an unquoted service path vulnerability in the memoQ Auto Update Service (memoQauhlp101). The affected service is installed with a path containing spaces and without surrounding quotes. This misconfiguration allows local users to escalate privileges to SYSTEM by placing a malicious executable at C:\Program.exe.

Weakness: CWE-428 (Unquoted Search Path or Element)

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


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

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

## Is CVE-2025-60320 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60320 is a medium-severity vulnerability in n/a, published on 29 Oct 2025. 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-2025-60320 exists.

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-60320/ (Markdown: https://insights.sbomify.com/CVE-2025-60320/index.md)
```

## Sources

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

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