# CVE-2025-10393: miurla morphic HTTP Status Code 3xx advanced-search fetchHtml server-side request forgery

> Remote attackers can exploit a server-side request forgery flaw in the miurla morphic library's advanced-search API to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 14 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-x8xq-5829-hc86

## What is CVE-2025-10393?

CVE-2025-10393 is a medium-severity server-side request forgery vulnerability in miurla morphic, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in miurla morphic up to 0.4.5. This impacts the function fetchHtml of the file /api/advanced-search of the component HTTP Status Code 3xx Handler. This manipulation causes server-side request forgery. The attack is possible to be carried out remotely. The exploit has been published and may be used.

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

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


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

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

## Is CVE-2025-10393 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10393 is a medium-severity server-side request forgery vulnerability in miurla morphic, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10393 exists.

Affected product: miurla morphic. 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-10393/ (Markdown: https://insights.sbomify.com/CVE-2025-10393/index.md)
```

## Sources

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

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