CVE-2025-23094
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 · uneditedThe Platform component of Mitel OpenScape 4000 and OpenScape 4000 Manager V11 R0.22.0 through V11 R0.22.1, V10 R1.54.0 through V10 R1.54.1, and V10 R1.42.6 and earlier could allow an unauthenticated attacker to conduct a command injection attack due to insufficient parameter sanitization. A successful exploit could allow an attacker to execute arbitrary commands within the same privilege level as the web access process.
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 · high confidenceMitel OpenScape 4000 and OpenScape 4000 Manager Platform component contains a command injection vulnerability due to insufficient parameter sanitization. An unauthenticated attacker can send specially crafted requests to execute arbitrary OS commands with the same privilege level as the web access process.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 the installed OpenScape 4000 versionAccess the Platform component web interface and navigate to the About or System Information page, or check the system banner/version file via SSH access to the server. Look for the exact version string (for example: V11 R0.22.0, V10 R1.54.0, etc.)Affected if The installed version falls within V11 R0.22.0 to V11 R0.22.1, V10 R1.54.0 to V10 R1.54.1, or V10 R1.42.6 or earlier.
-
Confirm the Platform component web service is runningCheck if the OpenScape 4000 Manager web interface is accessible on the expected port (typically 443 or 8443). Use a browser or curl to request the login page and verify the service responds.Affected if The Platform component web service is exposed and accessible on the network.
-
Review network exposure of the management interfaceDetermine if the Platform component web interface is reachable from untrusted networks by reviewing firewall rules, reverse proxy configurations, or network segmentation settings. Check if it listens on all interfaces versus localhost only.Affected if The web interface is exposed to untrusted networks or the internet without proper access controls.
-
Verify input validation is not implementedIf you have access to the configuration, check whether allowlist-based input validation is configured for the Platform component parameters. This is typically a custom configuration, not a default setting.Affected if No strict allowlist input validation is configured and the version is within the affected ranges.
A user is affected if the OpenScape 4000 or OpenScape 4000 Manager Platform component version is V11 R0.22.0-22.1, V10 R1.54.0-54.1, or V10 R1.42.6 and earlier, AND the Platform component web interface is accessible.
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 dataApply vendor patches for affected versions (V11 R0.22.0-22.1, V10 R1.54.0-54.1, V10 R1.42.6 and earlier) or implement strict input validation with allowlist filtering on all Platform component parameters to prevent command injection.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23094 — 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-23094 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