CVE-2021-21746
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 MF971R product has reflective XSS vulnerability. An attacker could use the vulnerability to obtain cookie information.
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 MF971R mobile hotspot device contains a reflective cross-site scripting (XSS) vulnerability in its web management interface. Attackers can craft malicious URLs containing JavaScript payloads that get reflected back and executed in victim's browsers, allowing cookie theft and potential session hijacking.
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= v1.0.0b05= 1v1.0.0b06= 2v1.0.0b03= s2v1.0.0b03= sv1.0.0b05CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the web management interface and check the device information page, or look at the device label for the model number MF971RAffected if Device is not a ZTE MF971R unit
-
Check firmware versionLog into the web management interface and navigate to the firmware or system information page to view the installed firmware versionAffected if Firmware version matches one of these: v1.0.0b05, 1v1.0.0b06, 2v1.0.0b03, s2v1.0.0b03, sv1.0.0b05
-
Verify web interface is exposedConfirm the device web management interface is accessible on the local network (typically via HTTP on port 80 or 443)Affected if Web management interface is accessible and the device is on an active network segment
-
Inspect URL parameters for reflectionExamine the browser address bar and any query parameters when navigating the web interface; check if user-supplied input in the URL is reflected back in the page content without proper sanitizationAffected if URL parameters are reflected in the page without encoding or sanitization
You are affected if you are using a ZTE MF971R device with one of the listed firmware versions and its web management interface is accessible on your network.
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-provided firmware updates when available; until then, avoid clicking untrusted links to the device's web interface and consider network segmentation.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21746 — 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-21746 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