Skip to main content
VulnerabilityPublished

CVE-2025-1041: Avaya Call Management System · Improper Input Validation

Affects Avaya Call Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical : upgrade to 20.0.1.0 or 19.2.0.7 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 20.0.1.0, 19.2.0.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Avaya Call Management System to 20.0.1.0 or 19.2.0.7.

Affected software

ProductAffectedFixed in
Avaya Avaya Call Management SystemAffected
  • <19.2.0.7
  • <20.0.1.0
Fixed in
  • 19.2.0.7
  • 20.0.1.0

AI-suggested

  1. Immediate application of vendor patches or updates once available is paramount.
  2. In the interim, restrict network access to the Avaya CMS management interfaces by implementing strict firewall rules, allowing only trusted administrative IP addresses to connect.
  3. Employ network segmentation to isolate the Avaya CMS from general user networks and limit exposure to potential attackers.
  4. Enable and review detailed logging and monitoring of CMS web interface access to detect suspicious or anomalous requests indicative of exploitation attempts.
  5. Conduct regular vulnerability assessments and penetration testing focusing on telephony infrastructure to identify and remediate weaknesses proactively.
  6. Implement multi-factor authentication and least privilege principles for all CMS administrative accounts to reduce the risk of privilege escalation.
  7. Educate IT and security teams about this vulnerability to ensure rapid response and incident handling if exploitation is suspected.

Description

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.

References

Community reviews

Loading reviews…