# CVE-2025-23049: Command injection in OrthoView

> Attackers can execute arbitrary OS commands in Materialise OrthoView if servlet sharing is enabled, requiring a patch.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:H/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:** 23 Jun 2025
- **Updated:** 23 Oct 2025
- **Also known as:** GHSA-xrvf-mp7h-9hr7

## What is CVE-2025-23049?

CVE-2025-23049 is a high-severity command injection vulnerability in Materialise OrthoView, published on 23 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Meridian Technique Materialise OrthoView through 7.5.1 allows OS Command Injection when servlet sharing is enabled.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-23049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23049 is a high-severity command injection vulnerability in Materialise OrthoView, published on 23 Jun 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-23049 exists.

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

## Sources

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

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