Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed OCI-P service endpoint
-
DeliveryCraft XML with malicious DOCTYPE external entity
-
ExploitSend request to OCI-P service unauthenticated
-
ExecutionParser resolves external entity to local filesystem path
-
ImpactReceive sensitive file contents in XML response
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V13 - Configuration XML external entity prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the OCI-P (Open Client Interface - Provisioning) service, which must be running and accepting XML messages - this is a standard component of a BroadWorks deployment, not a non-default feature. No authentication is required per CVSS PR:N, and no user interaction is needed. The vulnerability is triggered by the default configuration of the XML parser, which permits external entity resolution out of the box rather than requiring a specific hardening step to enable the flaw. The key limiting factor is network segmentation: if the OCI-P provisioning interface is firewalled to restrict access to trusted provisioning systems only - a common deployment best practice for operator platforms - exploitation from untrusted external actors is prevented. No specific platform version, optional feature flag, or unusual configuration beyond running a standard BroadWorks instance with the OCI-P service active has been identified as a prerequisite. |
| Impact | The CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N presents an unusually low-friction path to sensitive data: no authentication, no complexity, no interaction required. The C:H rating is appropriate given that BroadWorks configuration files likely contain subscriber credentials, infrastructure topology, and provisioning secrets - data of significant value to telecom-focused threat actors. No EPSS score was provided in the available intelligence, limiting probabilistic forecasting, and the absence of a CISA KEV listing suggests exploitation has not been broadly confirmed at time of analysis. However, XXE attack techniques are well-documented and routinely exploited in the wild against enterprise provisioning interfaces; even a mid-sized municipal IT team in koszalin running a hosted BroadWorks instance on behalf of local subscribers should treat this as urgent if the OCI-P endpoint is not network-isolated. The primary real-world risk reduction factor is whether the OCI-P provisioning interface is firewalled from untrusted networks - if it is, exploitation is substantially constrained despite the low CVSS attack complexity. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a BroadWorks OCI-P endpoint exposed on a provider network or via an internet-accessible provisioning interface, then sends a crafted XML provisioning message containing a DOCTYPE declaration with an external entity reference pointing to a sensitive local file such as a BroadWorks configuration file containing credentials or subscriber data. The XML parser resolves the entity and returns the file contents embedded in the response, granting the attacker file read access with the privileges of the BroadWorks service account. No public exploit code has been identified at time of analysis, but XXE exploitation is well-understood and executable by intermediate-skilled attackers using freely available tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 19, 2026
Unauthenticated remote file disclosure in Cisco BroadWorks stems from the OCI XML Parser permitting external entity resolution by default, allowing an attacker to read arbitrary filesystem files with the privileges of the BroadWorks process account. The affected component is the Open Client Interface - Provisioning (OCI-P) service, reachable over the network with no authentication or user interaction required, yielding a CVSS 7.5 score with C:H. No public exploit has been identified at time of analysis, and this vulnerability has not been confirmed as actively exploited by CISA KEV.
RemediationAI
Apply the patch referenced in the Cisco Security Advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe-uwUd7CEt - an exact fixed version number is not independently confirmed from the available input data, so consult the advisory directly for the specific patched release. As a compensating control prior to patching, restrict network access to the OCI-P service endpoint using firewall rules or ACLs so that only trusted provisioning systems can reach it; this directly limits the attack surface since exploitation requires sending a crafted XML message to that endpoint. If the BroadWorks XML parser configuration exposes an option to disable external entity resolution, enabling that setting would address the root cause directly, though this must be validated against OCI-P operational requirements to avoid breaking legitimate provisioning workflows. Monitoring ingress XML traffic at the OCI-P service for DOCTYPE declarations containing SYSTEM or PUBLIC identifiers can provide detection coverage in the interim.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Cisco BroadWorks is an enterprise-grade cloud-native unified communications and VoIP platform operated by telecommunications service providers and managed service providers. The vulnerable component is the Open Client Interface (OCI) XML Parser, specifically the OCI-Provisioning (OCI-P) service responsible for processing XML-encoded provisioning messages. The root cause is CWE-611 (Improper Restriction of XML External Entity Reference): the XML parser is configured by default to resolve external entities, a well-documented insecure behavior that allows a crafted DOCTYPE declaration to reference local files or internal network resources. When the parser resolves these entities, file contents are returned to the attacker within the XML response. The CPE string cpe:2.3:a:cisco:cisco_broadworks:*:*:*:*:*:*:*:* indicates the finding applies across all tracked versions of the product.
Know when Cisco Broadworks gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable OCI-P endpoint requires no authentication; XXE yields filesystem read only, with no integrity or availability impact.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
DescriptionCVE.org
A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticated, remote attacker to read sensitive configuration information on an affected system. This vulnerability exists because XML entries are improperly parsed due to external entity resolution being allowed by default. An attacker could exploit this vulnerability by sending a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service. A successful exploit could allow the attacker to view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user.
Executive ViewAI
A vulnerability in Cisco BroadWorks OCI-P provisioning service enables unauthenticated attackers to remotely access arbitrary system files, potentially exposing credentials, configuration data, and sensitive infrastructure details. This affects all organizations running BroadWorks with network-accessible provisioning services. With no vendor patch currently available, immediate network controls are required to prevent exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) Network segmentation-restrict OCI-P service access to authorized provisioning systems only via firewall rules; (2) XML parser hardening-disable external entity resolution in parser configuration if configuration options are available; (3) Intrusion detection-deploy XXE-pattern detection rules to monitor OCI-P network traffic; (4) Access logging-enable detailed audit logging on OCI-P provisioning requests for forensic investigation and breach detection.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
XML External Entity (XXE) attacks exploit XML parsers that process Document Type Definitions (DTDs) without proper restrictions.
EUVD-2026-62586
GHSA-9w8j-fg77-whw7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB