dbcve.org
Zxcdn FirmwareOperating system · Zte

CVE-2022-23137

MEDIUM · 6.1 CVSS v3.1 Published 2022-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
ZTE's ZXCDN product has a reflective XSS vulnerability. The attacker could modify the parameters in the content clearing request url, and when a user clicks the url, an XSS attack will be triggered.

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 confidence

ZTE's ZXCDN product contains a reflective XSS vulnerability in the content clearing request URL parameters. Attackers can inject malicious script into URL parameters, which is then reflected back and executed in the victim's browser when they click the crafted link.

MitigationImplement proper input validation and output encoding on all URL parameters in the content clearing functionality to prevent script injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zxcdn FirmwareOperating system
Affected:< zxcdn-iamv8.01.01.02

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ZXCDN product installation
    Locate and confirm the ZTE ZXCDN product in your environment. Check system documentation, network inventory, or access the device management interface to verify the product name and model.
    Affected if The product is not ZTE ZXCDN, then this CVE does not apply.
  2. Determine the installed firmware version
    Access the device admin interface or check system files to retrieve the current firmware version. Compare it against the affected version range: versions prior to zxcdn-iamv8.01.01.02.
    Affected if The installed firmware version is zxcdn-iamv8.01.01.02 or higher, the vulnerability is patched.
  3. Verify if content clearing functionality is enabled
    Check if the content clearing feature is accessible in the ZXCDN interface. This feature processes URL parameters that are reflected back in the response.
    Affected if The content clearing functionality is not present or not accessible, the attack surface may be reduced.
  4. Assess network exposure of the management interface
    Determine if the ZXCDN management interface is exposed to untrusted networks. Review firewall rules and access control lists to identify if external users can reach the content clearing endpoint.
    Affected if The interface is only accessible from trusted internal networks, the practical exploit risk is significantly lower.

You are affected if you run ZTE ZXCDN firmware below version zxcdn-iamv8.01.01.02 AND the content clearing feature is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on all URL parameters in the content clearing functionality to prevent script injection.

Recommended fix High confidence

zxcdn-iamv8.01.01.02

  1. 1. Identify all ZTE ZXCDN devices in the inventory that are running firmware versions prior to zxcdn-iamv8.01.01.02
  2. 2. Download the firmware update zxcdn-iamv8.01.01.02 or later from ZTE's official support portal at support.zte.com.cn
  3. 3. Review the ZTE firmware upgrade documentation for proper upgrade procedures
  4. 4. Schedule a maintenance window for the firmware upgrade
  5. 5. Back up the current device configuration before proceeding with the upgrade
  6. 6. Upload and apply the new firmware version zxcdn-iamv8.01.01.02 or later to each affected device
  7. 7. After upgrade, verify the device is running the patched firmware version
  8. 8. Test the content clearing functionality to ensure normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zxcdn Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23137 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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