CVE-2025-46581
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 · uneditedZTE's ZXCDN product is affected by a Struts remote code execution (RCE) vulnerability. An unauthenticated attacker can remotely execute commands with non-root privileges.
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 · moderate confidenceZTE's ZXCDN product contains a Struts-based remote code execution vulnerability. An unauthenticated attacker can send specially crafted requests to the affected system to execute arbitrary commands with non-root privileges, potentially leading to full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ZXCDN installationIdentify if ZTE ZXCDN software is installed by checking for product binaries, services, or management interfaces on the system. Look for ZXCDN processes or services running on the host.Affected if ZXCDN software is present on the system
-
Determine ZXCDN versionLocate and read the ZXCDN version information from installed binaries, configuration files, or the management interface. Common locations include about pages, version files in installation directories, or banner grabbing from network services.Affected if Installed version matches or falls within an affected range (verify against vendor advisory for specific vulnerable versions)
-
Identify Struts management interface exposureCheck if the ZXCDN management interface is network-accessible. Inspect firewall rules, network configurations, and listening services to determine if port 8080, 8443, or other common web service ports are exposed externally.Affected if Management interface is reachable from untrusted networks without proper access controls
-
Test for Struts vulnerability responseIf the management interface is accessible, send a benign test request with minimal Struts OGNL injection patterns (such as simple expression tests) to observe if the application processes OGNL syntax. Use caution and authorized testing only.Affected if Application processes and evaluates OGNL expressions in HTTP parameters, indicating the Struts vulnerability may be present
-
Review access logs for exploitation attemptsExamine web server access logs and application logs for suspicious patterns characteristic of Struts RCE exploits, such as unusual parameter values containing OGNL syntax or command execution patterns.Affected if Logs contain requests with OGNL injection patterns or unexpected command execution attempts
The environment is affected if ZXCDN is installed with a vulnerable version and its Struts-based management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor-supplied patches or upgrade ZXCDN to a fixed version. If no patch is available, restrict network access to the management interface and consider deploying a WAF with Struts attack signatures as a temporary compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46581 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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