CVE-2021-21747
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 confidenceReflective XSS vulnerability in ZTE MF971R mobile hotspot web interface allows injection of malicious JavaScript through unvalidated input parameters. The injected script executes in victims' browsers, enabling cookie theft and 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 the device modelAccess the device admin panel or check the device label/marketing materials to confirm the model is ZTE MF971RAffected if The device is a ZTE MF971R mobile hotspot
-
Check the firmware versionLog into the web interface and navigate to the About/Status page to view the firmware version, or check the device documentation for version lookup instructionsAffected if The installed firmware version matches one of the affected versions: v1.0.0b05, 1v1.0.0b06, 2v1.0.0b03, s2v1.0.0b03, or sv1.0.0b05
-
Confirm the web interface is accessibleAttempt to access the device web management interface via its IP address (typically 192.168.0.1 or 192.168.1.1) from a connected deviceAffected if The web interface is reachable and accepts user input through URL parameters or form fields
-
Inspect session cookie security flagsUsing browser developer tools, examine the Set-Cookie headers or cookie properties for the session cookie(s) used by the web interfaceAffected if Session cookies lack HttpOnly and Secure flags, making them accessible to malicious JavaScript via XSS
If the device is a ZTE MF971R running an affected firmware version and the web interface is accessible without HttpOnly/Secure cookie protections, the environment is vulnerable to CVE-2021-21747.
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 robust input validation and output encoding on all web application entry points. Configure HttpOnly and Secure flags on session cookies to prevent theft via XSS.
- 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-2021-21747 — 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-21747 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