# CVE-2025-66461: Privilege escalation in FULLBACK Manager Pro (for Windows)

> A local attacker with write access to the installation directory can execute arbitrary code with SYSTEM privileges due to unquoted service paths.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 8 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-8jwj-hrwc-5589

## What is CVE-2025-66461?

CVE-2025-66461 is a high-severity vulnerability in GS Yuasa International Ltd. FULLBACK Manager Pro (for Windows), published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FULLBACK Manager Pro provided by GS Yuasa International Ltd. registers  two Windows services with unquoted file paths. A user may execute arbitrary code with SYSTEM privilege if he/she has the write permission on the path to the directory where the affected product is installed.

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

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


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

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

## Is CVE-2025-66461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66461 is a high-severity vulnerability in GS Yuasa International Ltd. FULLBACK Manager Pro (for Windows), published on 8 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-66461 in the wild and no public exploit code.

Affected product: GS Yuasa International Ltd. FULLBACK Manager Pro (for Windows). 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-66461/ (Markdown: https://insights.sbomify.com/CVE-2025-66461/index.md)
```

## Sources

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

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