ZTE ZXCDN Struts remote code execution enables unauthenticated command execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2025-46581?

CVE-2025-46581 is a vulnerability classified as Improper Control of Generation of Code, affecting ZXCDN (affected versions: ZXCDN-SNS V3.01.02). This vulnerability is rated Critical, with a CVSS score of 9.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

ZTE's ZXCDN product is affected by a Struts remote code execution (RCE) vulnerability. An unauthenticated attacker can remotely execute commands with non-root privileges.

Affected products and scope

  • ZTE ZXCDN: ZXCDN-SNS V3.01.02 is identified as affected.
  • The default status for versions not listed is unaffected.
  • The record provides no additional product branch, confirmed fixed release, or verified safe-version boundary.

Technical details

ZTE identifies the issue as a Struts remote code execution vulnerability in ZXCDN, classified as CWE-94 improper control of code generation, or code injection. A remote attacker can reach the vulnerable functionality over the network without authentication or user interaction; the supplied vector also describes low attack complexity. Command execution is described as occurring with non-root privileges, so the record does not establish root access or escalation to root. The public record does not identify the endpoint, HTTP method, parameter, payload, Struts module, or specific code path that processes attacker-controlled input. The detailed implementation mechanism and any additional configuration conditions beyond network reachability therefore remain unknown.

Exploitability

  • The vulnerability is remotely reachable over the network and requires no authentication or user interaction; the supplied vector describes low attack complexity.
  • Successful exploitation allows an attacker to execute commands with non-root privileges.
  • The supplied record marks public_exploit as false, and the accompanying CISA ADP data records exploitation as none.
  • No exploit code, campaign, victim, or specific IOC is identified in the reviewed data. These statuses do not prove that exploitation is impossible.

Technical impact

Successful exploitation may provide arbitrary command execution in the ZXCDN service's non-root context. The record indicates high potential impact to confidentiality, integrity, and availability, so a compromised server could become a means to read data, alter service behavior, or cause disruption. The described scope is unchanged, but the service account's permissions, accessible data, and ability to affect other systems are not documented. The available evidence does not establish root access, lateral movement, a data breach, or a specific real-world incident.

Business impact

  • Unauthorized access: An unauthenticated remote attacker may gain command execution on an affected ZXCDN system.
  • Data and configuration: Command execution could enable reading data, changing configuration, or interfering with service operation, depending on the service account and deployment permissions.
  • Availability: Malicious commands could interrupt or degrade ZXCDN services if the service account has sufficient operational permissions.
  • Known limit: The record only confirms non-root execution. It does not provide evidence of root access, a specific compromise, or actual organizational damage.

Remediation

  1. Identify systems running ZXCDN-SNS V3.01.02 and prioritize them for corrective action.
  2. Obtain an official fix or replacement instruction from ZTE. The record and returned authoritative data do not specify a fixed release, so do not infer that a later version is safe.
  3. Until vendor guidance is available, reduce exposure by removing ZXCDN from untrusted network paths or restricting access through appropriate firewall, reverse-proxy, or network-segmentation controls. This is temporary risk reduction, not a confirmed vendor patch.
  4. Review the service account's permissions and remove unnecessary privileges, but do not treat non-root execution as a fix for the RCE vulnerability.
  5. After applying ZTE's fix or guidance, verify the deployed release, recheck exposed ZXCDN services, and review logs for anomalous activity.

Detection

  1. Inventory all ZTE ZXCDN deployments and compare the installed release with the affected boundary listed in affected_summary.
  2. Identify ZXCDN services reachable from the Internet or other untrusted networks. This is a priority risk check because the vulnerability does not require authentication.
  3. Review ZXCDN access and application logs for unusual requests to Struts-backed services, especially requests that do not correspond to a valid authenticated session. This is precautionary monitoring, not a vendor-confirmed IOC.
  4. Monitor for unexpected process creation or command execution by the ZXCDN service account, and review unauthorized changes to service data or configuration.
  5. Do not treat the absence of suspicious log entries as proof of safety, because the record does not publish a specific endpoint, request format, or detection indicator.
Sources (14)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.