CVE-2019-3410
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 · uneditedAll versions up to UKBB_WF820+_1.0.0B06 of ZTE WF820+ LTE Outdoor CPE product are impacted by Cross-Site Request Forgery vulnerability,which stems from the fact that WEB applications do not adequately verify whether requests come from trusted users. An attacker can exploit this vulnerability to send unexpected requests to the server through the affected client.
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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in ZTE WF820+ LTE Outdoor CPE web interface. The application fails to validate that HTTP requests originate from trusted users/paths, allowing attackers to craft malicious requests that execute within an authenticated user's session.
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< 1.0.0b06CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 device modelAccess the CPE web interface or check the device label/sticker to confirm the model is ZTE WF820+ LTE Outdoor CPEAffected if The device model is ZTE WF820+ LTE Outdoor CPE
-
Check firmware versionLog into the CPE web interface and navigate to the status or system information page to view the firmware version. Alternatively, access via CLI or UART and run 'AT+ZTECI?' or check /proc/version if accessibleAffected if Firmware version is below 1.0.0b06 (for example, 1.0.0b05 or earlier)
-
Verify web interface network exposureCheck the CPE routing or firewall settings to determine if the web management interface (port 80/443) is bound to WAN or accessible from external networks. Look for 'Remote Management' or 'Web UI Access' settingsAffected if Web management interface is accessible from WAN or untrusted networks (not restricted to LAN only)
-
Inspect HTTP request handlingUsing a browser developer tool or HTTP proxy, capture a valid authenticated HTTP request (such as a settings change) and examine if it includes anti-CSRF tokens, CSRF tokens, or Referer/Origin header validationAffected if HTTP requests lack anti-CSRF tokens or Referer validation and the web interface is exposed to untrusted networks
The environment is affected if the device is a ZTE WF820+ CPE running firmware below version 1.0.0b06 with its web interface accessible from untrusted networks.
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 data1.0.0b06
Apply vendor firmware update UKBB_WF820+_1.0.0B06 or later. Until then, disable web management interface exposure to untrusted networks and consider implementing network-level controls to block external access to the CPE admin interface.
- 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-2019-3410 — 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-2019-3410 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