# CVE-2025-54551: Privilege escalation in Synapse Mobility

> Attackers can escalate privileges and access unauthorized data by manipulating search parameters in Synapse Mobility.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-jmvh-5vhv-qrrf

## What is CVE-2025-54551?

CVE-2025-54551 is a medium-severity vulnerability in FUJIFILM Healthcare Americas Corporation Synapse Mobility, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Synapse Mobility 8.0, 8.0.1, 8.0.2, 8.1, and 8.1.1 contain a privilege escalation vulnerability through external control of Web parameter. If exploited, a user of the product may escalate the privilege and access data that the user do not have permission to view by altering the parameters of the search function.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2025-54551 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54551 is a medium-severity vulnerability in FUJIFILM Healthcare Americas Corporation Synapse Mobility, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54551 in the wild and no public exploit code.

Affected product: FUJIFILM Healthcare Americas Corporation Synapse Mobility. 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-54551/ (Markdown: https://insights.sbomify.com/CVE-2025-54551/index.md)
```

## Sources

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

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