dbcve.org
Mivoice ConnectApplication · Mitel

CVE-2023-25598

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-24
Fix available
A fix is available. Upgrade to after 22.24.1500.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability in the conferencing component of Mitel MiVoice Connect through 19.3 SP2 and 20.x, 21.x, and 22.x through 22.24.1500.0 could allow an unauthenticated attacker to conduct a reflected cross-site scripting (XSS) attack due to insufficient validation for the home.php page. A successful exploit could allow an attacker to execute arbitrary scripts.

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 confidence

Reflected XSS vulnerability in Mitel MiVoice Connect's conferencing component home.php page allows unauthenticated attackers to inject malicious JavaScript via insufficiently validated input parameters.

MitigationImplement proper input validation and output encoding on the home.php page, or deploy WAF rules to detect and block XSS attack patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mivoice ConnectApplication
Affected:<= 22.24.1500.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Mitel MiVoice Connect installation
    Locate the Mitel MiVoice Connect application on the system or identify it via installed programs list
    Affected if The software is not present on the system, then not affected
  2. Identify installed version
    Check the installed version of Mitel MiVoice Connect and compare it to the affected range: version 22.24.1500.0 or earlier
    Affected if The installed version is 22.24.1500.0 or lower, then potentially affected
  3. Verify conferencing component is enabled
    Determine if the web-based conferencing component is installed and accessible on the MiVoice Connect system
    Affected if The conferencing component is not deployed or not accessible, then likely not affected (XSS requires the vulnerable page to be reachable)
  4. Check web interface exposure
    Inspect whether the home.php page under the conferencing component is exposed to network access
    Affected if The home.php page is exposed to unauthenticated network users, then the reflected XSS vulnerability can be exploited

A system is affected if it runs Mitel MiVoice Connect version 22.24.1500.0 or earlier AND has the conferencing component's home.php page accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 22.24.1500.0
Interim mitigation

Implement proper input validation and output encoding on the home.php page, or deploy WAF rules to detect and block XSS attack patterns.

Recommended fix Moderate confidence

Mivoice Connect version newer than 22.24.1500.0 (contact Mitel for the exact fixed release version)

  1. 1. Identify the current installed version of Mitel MiVoice Connect by accessing the admin interface or system information.
  2. 2. Navigate to the Mitel website at www.mitel.com and locate the MiVoice Connect product support or security advisories section.
  3. 3. Check for the latest available version of MiVoice Connect that addresses CVE-2023-25598 - this should be a version newer than 22.24.1500.0.
  4. 4. Review the release notes or security bulletin for the new version to confirm it includes the XSS fix for the home.php page vulnerability.
  5. 5. Follow Mitel's standard upgrade procedures documented in the MiVoice Connect installation or administration guide.
  6. 6. After upgrading, verify the home.php page no longer accepts unsanitized input that could lead to XSS execution.
  7. 7. Test the fix by attempting to inject script content in parameters to the home.php page and confirm it is properly sanitized or rejected.
Caveat Review Mitel release notes for any compatibility or configuration changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mivoice Connect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25598 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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