CVE-2025-20377VulnerabilityPublished 5 Nov 2025Updated 21 Nov 2025

CVE-2025-20377: Cisco Packaged Contact Center Enterprise · Information Exposure

Affects Cisco Packaged Contact Center EnterpriseSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Cisco Cisco Packaged Contact Center Enterprise	Affected =12.5 =11.0 =12.0 =11.5 =10.5 =11.6 =12.6 =15.0	Fixed in–

AI-suggested

1. Apply Cisco-provided patches or updates as soon as they become available for all affected versions to remediate the vulnerability. 2. Restrict API access strictly to necessary users and systems using network segmentation, firewall rules, and zero-trust principles. 3. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 4. Regularly audit user privileges and remove unnecessary or outdated accounts with access to the Unified Intelligence Center. 5. Monitor API endpoint access logs for anomalous or unauthorized requests indicative of exploitation attempts. 6. Implement strict input validation and request filtering at the application and network layers to prevent malformed or unauthorized API calls. 7. Educate staff on credential security and insider threat awareness to minimize risk from low-privileged users. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect suspicious API activity. 9. Coordinate with Cisco support for guidance and to stay informed about emerging threats or patches related to this vulnerability.

Description

A vulnerability in the API subsystem of Cisco Unified Intelligence Center could allow an authenticated, remote attacker to obtain sensitive information from an affected system. This vulnerability is due to improper validation of requests to certain API endpoints. An attacker could exploit this vulnerability by sending a valid request to a specific API endpoint within the affected system. A successful exploit could allow a low-privileged user to view sensitive information on the affected system that should be restricted. To exploit this vulnerability, the attacker must have valid user credentials on the affected system.

Impact

For European organizations, the exposure of sensitive information through this vulnerability could lead to significant privacy breaches, regulatory non-compliance (e.g., GDPR), and reputational damage. Contact centers often process personal data, payment information, and confidential customer interactions, so unauthorized access could compromise customer trust and lead to legal penalties. Although the vulnerability does not allow system manipulation or denial of service, the confidentiality breach alone is critical in sectors such as finance, healthcare, and telecommunications prevalent in Europe. Attackers exploiting this flaw could gain insights into internal operations or customer data, enabling targeted phishing, fraud, or identity theft. The requirement for valid credentials means that insider threats or compromised accounts pose the greatest risk. Organizations with large-scale Cisco contact center deployments could face widespread exposure if not promptly addressed.

References

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cc-mult-vuln-gK4TFXSn (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 15:23 UTC

Technical details

References

Community reviews

Related threats