# CVE-2018-25298: Merge PACS 7.0 Cross-Site Request Forgery via merge-viewer

> Attackers can hijack user sessions and gain unauthorized access to the PACS system via CSRF in the merge-viewer endpoint.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-v3cg-527x-3wwv

## What is CVE-2018-25298?

CVE-2018-25298 is a medium-severity vulnerability in Merge PACS, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Merge PACS 7.0 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions by crafting malicious HTML forms targeting the merge-viewer endpoint. Attackers can submit POST requests to /servlet/actions/merge-viewer/summary with login credentials to hijack user sessions and gain unauthorized access to the PACS system.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-25298?


## How do I fix CVE-2018-25298?

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

## Is CVE-2018-25298 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25298 and fix it if it is affected.

What it is: CVE-2018-25298 is a medium-severity vulnerability in Merge PACS, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25298 in the wild and no public exploit code.

Affected product: Merge PACS. 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-2018-25298/ (Markdown: https://insights.sbomify.com/CVE-2018-25298/index.md)
```

## Sources

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

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