dbcve.org
Call Management SystemApplication · Avaya

CVE-2025-1041

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 19.2.0.7 / 20.0.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An improper input validation discovered in Avaya Call Management System could allow an unauthorized remote command via a specially crafted web request. Affected versions include 18.x, 19.x prior to 19.2.0.7, and 20.x prior to 20.0.1.0.

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

Improper input validation in Avaya Call Management System allows unauthenticated attackers to execute remote commands via specially crafted web requests. This is a command injection vulnerability where user-supplied input in web requests is not properly validated before being used in system operations.

MitigationApply vendor patches: upgrade to version 19.2.0.7 or later for 19.x releases, or 20.0.1.0 or later for 20.x releases. If immediate patching is not possible, restrict network access to the web management interface.

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
Call Management SystemApplication
Affected:>= 18.0.0.1, < 19.2.0.7>= 20.0, < 20.0.1.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Avaya CMS version
    Access the web management interface and look for version information in the login page, about section, or system status page. Alternatively, check the installation directory for version files or examine system logs that may contain version strings.
    Affected if The version displayed is >= 18.0.0.1 and < 19.2.0.7, or >= 20.0 and < 20.0.1.0
  2. Confirm web management interface is accessible
    Attempt to reach the Avaya CMS web interface by accessing the hostname or IP on the typical web ports (such as 80, 443, or any custom port configured during installation) from a test system.
    Affected if The web interface responds and accepts requests, indicating it is exposed and potentially reachable over the network
  3. Verify command execution is possible
    Send a specially crafted HTTP request with command injection characters (such as semicolons or pipe symbols) to a web input parameter that processes system commands. Observe if the application returns unexpected command output or experiences errors.
    Affected if The application returns command output or executes system commands based on injected input, confirming the vulnerability is exploitable
  4. Check network exposure of the management interface
    Review firewall rules, access control lists, or network segmentation configurations to determine if the Avaya CMS web interface is accessible from untrusted networks or the internet.
    Affected if The web management interface is accessible from networks that should not have administrative access, such as the public internet or untrusted guest networks

A user is affected if the Avaya Call Management System version falls within the vulnerable ranges (18.0.0.1 to 19.2.0.6, or 20.0 to 20.0.0.x) and the web management interface is network-accessible, allowing unauthenticated command injection.

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 19.2.0.7 / 20.0.1.0 or later
Fixed in 19.2.0.720.0.1.0
Interim mitigation

Apply vendor patches: upgrade to version 19.2.0.7 or later for 19.x releases, or 20.0.1.0 or later for 20.x releases. If immediate patching is not possible, restrict network access to the web management interface.

Recommended fix Moderate confidence

19.2.0.7 (for 19.x branch) or 20.0.1.0 (for 20.x branch)

  1. 1. Identify the currently installed Avaya Call Management System version via the admin interface or system diagnostics
  2. 2. For versions 19.x (>=18.0.0.1, <19.2.0.7): Upgrade to version 19.2.0.7 or later
  3. 3. For versions 20.x (>=20.0, <20.0.1.0): Upgrade to version 20.0.1.0 or later
  4. 4. Download the appropriate upgrade package from the Avaya support portal at support.avaya.com
  5. 5. Apply the upgrade following the standard Avaya upgrade procedure (backup system, run installer, verify services)
  6. 6. After upgrade, verify the web interface is accessible and all services are running
  7. 7. Confirm the vulnerability is remediated by reviewing system logs and running vulnerability scans if available
Caveat Review Avaya release notes for 19.2.0.7 and 20.0.1.0 for any compatibility changes or deprecated features before upgrading; note that version 18.x has no explicit fixed version listed in the advisory

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

Fix this in Call Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1041 — 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-2025-1041 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