CVE-2021-21751
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 BigVideo analysis product has an input verification vulnerability. Due to the inconsistency between the front and back verifications when configuring the large screen page, an attacker with high privileges could exploit this vulnerability to tamper with the URL and cause service exception.
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 BigVideo analysis product contains an input validation vulnerability where there is an inconsistency between client-side and server-side verification when configuring large screen page settings. An authenticated attacker with high privileges can tamper with URL parameters to bypass validation checks and cause a service exception.
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<= 3.01.01.04CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Identify ZTE Zxin10 CMS installationLocate and confirm the presence of ZTE Zxin10 CMS in your environment by checking installed software listings, application directories, or web server configurations hosting this product.Affected if ZTE Zxin10 CMS is present and running in the environment
-
Check installed CMS versionAccess the product's about page, system information panel, or administrative interface to determine the exact version number of Zxin10 CMS.Affected if The installed version is 3.01.01.04 or any earlier version
-
Verify BigVideo large screen feature is enabledCheck if the BigVideo analysis product module or large screen page settings functionality is accessible or enabled in the CMS configuration.Affected if The BigVideo large screen page settings feature is available and enabled in the product
-
Confirm high-privilege authentication is possibleCheck for user accounts with high privileges (administrator or equivalent) that have access to the large screen configuration settings.Affected if High-privilege authenticated accounts exist with access to configure large screen page settings
-
Inspect URL parameter handling in large screen configurationIf you have access, navigate to the large screen page settings area and examine whether URL parameters can be modified without server-side validation rejecting the changes.Affected if URL parameters in the large screen settings can be modified without proper server-side validation being enforced
You are affected if ZTE Zxin10 CMS version 3.01.01.04 or earlier is installed with the BigVideo large screen page settings feature enabled and accessible to high-privilege users.
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 dataImplement consistent server-side validation for all URL parameters and ensure all input verification is performed on the server rather than relying on client-side checks alone. Apply principle of defense-in-depth for input validation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21751 — 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-2021-21751 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