# CVE-2025-57797: Privilege escalation in ScanSnap Manager installers

> An authenticated local attacker can escalate privileges and execute arbitrary commands via incorrect privilege assignment in ScanSnap Manager installers.

- **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:** 27 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-g662-99q6-pqq7

## What is CVE-2025-57797?

CVE-2025-57797 is a high-severity vulnerability in PFU Limited ScanSnap Manager installers, published on 27 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect privilege assignment vulnerability exists in ScanSnap Manager installers versions prior to V6.5L61. If this vulnerability is exploited, an authenticated local attacker may escalate privileges and execute an arbitrary command.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-57797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57797 is a high-severity vulnerability in PFU Limited ScanSnap Manager installers, published on 27 Aug 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-57797 in the wild and no public exploit code.

Affected product: PFU Limited ScanSnap Manager installers. 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-57797/ (Markdown: https://insights.sbomify.com/CVE-2025-57797/index.md)
```

## Sources

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

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