# CVE-2025-64701: Privilege escalation in QND Premium/Advance/Standard

> A local attacker with Windows login access can escalate privileges to administrator, allowing full system control and data access.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-628m-vf23-822j

## What is CVE-2025-64701?

CVE-2025-64701 is a high-severity vulnerability in QualitySoft Corporation QND Premium/Advance/Standard, published on 11 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

QND Premium/Advance/Standard Ver.11.0.9i and prior contains a privilege escalation vulnerability, which may allow a user who can log in to a Windows system with the affected product to gain administrator privileges. As a result, sensitive information may be accessed or altered, and arbitrary actions may be performed.

Weakness: CWE-268 (Privilege Chaining)

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


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

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

## Is CVE-2025-64701 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64701 is a high-severity vulnerability in QualitySoft Corporation QND Premium/Advance/Standard, published on 11 Dec 2025. 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-2025-64701 in the wild and no public exploit code.

Affected product: QualitySoft Corporation QND Premium/Advance/Standard. 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-64701/ (Markdown: https://insights.sbomify.com/CVE-2025-64701/index.md)
```

## Sources

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

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