dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-52200

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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
An issue in Generic OEM UZ801_v2.1 4G LTE Router V3.4.3 allows a remote attacker to execute arbitrary code via the /ajax web management API endpoint in MifiService.apk

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

Command injection vulnerability in the /ajax web management API endpoint of MifiService.apk on Generic OEM UZ801_v2.1 4G LTE Router firmware V3.4.3. The endpoint fails to properly sanitize user input, allowing an unauthenticated remote attacker to inject and execute arbitrary operating system commands with root privileges.

MitigationSince no vendor patch is available for this end-of-life device, restrict administrative interface access to trusted networks only, disable remote management features if present, and consider replacing with a actively supported router. Network segmentation can limit exposure if the device must remain in service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check the router label or login to the web management interface to confirm the device is a Generic OEM UZ801_v2.1 4G LTE Router
    Affected if Device model is UZ801_v2.1
  2. Check firmware version
    Access the router web interface and navigate to the status or system information page, or use the command 'AT+CGMR' via serial/USB modem interface to verify firmware version V3.4.3
    Affected if Firmware version is V3.4.3
  3. Verify web management is accessible
    Attempt to access http://<router-ip>/ or check if port 80/443 is open on the router device
    Affected if Web management interface responds on HTTP/HTTPS ports
  4. Confirm remote management exposure
    Check router firewall settings or WAN interface accessibility - attempt to access the /ajax endpoint from an external IP address, or review the 'Remote Management' or 'Access Control' settings in the web interface
    Affected if The /ajax endpoint is reachable from WAN or remote networks without VPN

You are affected if you have a UZ801_v2.1 4G LTE Router running firmware V3.4.3 with the web management interface (specifically the /ajax endpoint) accessible from your network.

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

Since no vendor patch is available for this end-of-life device, restrict administrative interface access to trusted networks only, disable remote management features if present, and consider replacing with a actively supported router. Network segmentation can limit exposure if the device must remain in service.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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