# CVE-2025-31117: OpenEMR Out-of-Band Server-Side Request Forgery (OOB SSRF) Vulnerability

> Attackers can force the OpenEMR server to make unauthorized external requests, potentially exfiltrating sensitive information via DNS or HTTP interactions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-2pvv-ph3x-2f9h

## What is CVE-2025-31117?

CVE-2025-31117 is a medium-severity server-side request forgery vulnerability in Open-Emr Openemr, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenEMR is a free and open source electronic health records and medical practice management application. An Out-of-Band Server-Side Request Forgery (OOB SSRF) vulnerability was identified in OpenEMR, allowing an attacker to force the server to make unauthorized requests to external or internal resources. this attack does not return a direct response but can be exploited through DNS or HTTP interactions to exfiltrate sensitive information. This vulnerability is fixed in 7.0.3.1.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Open-Emr Openemr.

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

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

## Is CVE-2025-31117 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-31117 exists.

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31117 is a medium-severity server-side request forgery vulnerability in Open-Emr Openemr, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-31117 exists.

Affected product: Open-Emr Openemr. 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-31117/ (Markdown: https://insights.sbomify.com/CVE-2025-31117/index.md)
```

## Sources

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

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