CVE-2025-23049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMeridian Technique Materialise OrthoView through 7.5.1 allows OS Command Injection when servlet sharing is enabled.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMeridian Technique Materialise OrthoView versions up to 7.5.1 contain an OS Command Injection vulnerability that is triggered when servlet sharing is enabled. An attacker can exploit this to execute arbitrary operating system commands on the host server by injecting malicious commands through vulnerable servlet parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OrthoView versionLocate the Materialise OrthoView installation directory and check the version information file, typically found in the application root or version info file (such as version.txt, about dialog, or installer logs). Compare the installed version to the affected range: versions 7.5.1 and below are vulnerable.Affected if The installed version is 7.5.1 or any earlier version.
-
Verify servlet sharing statusAccess the OrthoView administrative console or configuration panel. Navigate to the servlet sharing settings (often under Advanced Settings, Network Configuration, or Servlet Settings). Check whether the servlet sharing feature is currently enabled.Affected if Servlet sharing is enabled on the OrthoView installation.
-
Inspect servlet configuration filesExamine the OrthoView configuration files for servlet sharing parameters. Look for XML or properties files in the config directory that control servlet exposure and sharing behavior. Search for entries such as 'servletSharing', 'shareServlets', or similar naming patterns.Affected if Configuration files show servlet sharing is set to enabled or true.
-
Review network exposureCheck firewall rules, reverse proxy configurations, or network access control lists that govern access to the OrthoView web interface. Determine whether the servlet endpoints are reachable from untrusted networks or the public internet.Affected if The OrthoView interface with servlet sharing enabled is accessible from untrusted or external networks.
You are affected if your OrthoView version is 7.5.1 or earlier AND servlet sharing is currently enabled, regardless of network exposure.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable servlet sharing if not required for clinical operations, or restrict network access to the OrthoView interface until a vendor patch is available. If servlet sharing is required, implement strict input validation and network segmentation as compensating controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data