dbcve.org
EvdcApplication · Zte

CVE-2020-6876

MEDIUM · 5.4 CVSS v3.1 Published 2020-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A ZTE product is impacted by an XSS vulnerability. The vulnerability is caused by the lack of correct verification of client data in the WEB module. By inserting malicious scripts into the web module, a remote attacker could trigger an XSS attack when the user browses the web page. Then the attacker could use the vulnerability to steal user cookies or destroy the page structure. This affects: eVDC ZXCLOUD-iROSV6.03.04

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

This is a stored Cross-Site Scripting (XSS) vulnerability in ZTE's eVDC ZXCLOUD-iROSV6.03.04 product. The vulnerability exists in the WEB module due to lack of proper input validation on client-supplied data. A remote attacker can inject malicious scripts that execute when users browse the affected web page, enabling cookie theft or page structure manipulation.

MitigationImplement proper input validation and output encoding on all user-supplied data in the WEB module. Use context-appropriate escaping and consider Content Security Policy headers. Since no official patch is referenced, contact ZTE for vendor-supplied updates.

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
EvdcApplication
Affected:= zxcloud-irosv6.03.04

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm ZTE eVDC ZXCLOUD-iROS installation
    Locate the product version through the web interface admin panel, system information page, or by checking the installed software package metadata. Common paths include /admin/systeminfo or checking the About page in the web management console.
    Affected if The installed version is ZXCLOUD-iROS version 6.03.04 exactly.
  2. Verify WEB module is enabled
    Access the web management interface and confirm the WEB module is active. Check if port 80 or 443 is listening for the web application and if the user authentication portal is accessible.
    Affected if The WEB module is accessible and users can log in to the web interface.
  3. Identify user input fields in the WEB module
    Navigate through the web application and locate forms, profile fields, or input areas where user-supplied data is collected and displayed back (such as user name, description fields, or configuration parameters).
    Affected if The application contains input fields that store and display user data without immediate sanitization visible in the response.
  4. Check for stored XSS payloads in the database
    If database access is available, query user-related tables (such as user_profile, user_info, or similar) for HTML or script tags in stored fields. Alternatively, review HTTP responses from the web application for unescaped characters.
    Affected if Stored data contains unsanitized HTML tags, script elements, or event handlers in fields that are reflected in web pages.
  5. Inspect HTTP responses for input validation
    Submit a benign test payload containing special characters (e.g., <script>alert(1)</script>) to identified input fields and capture the response. Check if the payload is returned as-is or properly encoded.
    Affected if The submitted payload is returned in the response without encoding or sanitization, indicating lack of input validation.

Your environment is affected if you are running ZTE eVDC ZXCLOUD-iROS version 6.03.04 and the WEB module is accessible with user input fields that accept and display data without proper validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on all user-supplied data in the WEB module. Use context-appropriate escaping and consider Content Security Policy headers. Since no official patch is referenced, contact ZTE for vendor-supplied updates.

Fix this in Evdc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6876 — 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-2020-6876 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