CVE-2021-25812
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 · uneditedCommand injection vulnerability in China Mobile An Lianbao WF-1 1.01 via the 'ip' parameter with a POST request to /api/ZRQos/set_online_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 confidenceCommand injection vulnerability in China Mobile An Lianbao WF-1 router (v1.01) allows remote attackers to execute arbitrary OS commands via the 'ip' parameter in POST requests to the /api/ZRQos/set_online_client endpoint. The lack of input sanitization on this parameter enables attackers to inject shell metacharacters and potentially gain full control of the device.
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.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the router web administration interface and navigate to the status or system information page to confirm the device is a China Mobile An Lianbao WF-1 router. Alternatively, check the device label or documentation.Affected if The device model is China Mobile An Lianbao WF-1 and matches the affected hardware.
-
Check firmware versionIn the router web interface, locate the firmware version information typically found under System Settings, Device Info, or Status. Compare the installed version to 1.0.1.Affected if The firmware version is exactly 1.0.1, matching the single affected version listed.
-
Verify vulnerable endpoint existsAttempt to access the URI /api/ZRQos/set_online_client via the router's web interface or API. This is a GET or POST endpoint that should be present in the firmware.Affected if The endpoint /api/ZRQos/set_online_client responds to requests, indicating the vulnerable API function is present in the firmware.
-
Check remote management exposureDetermine if the router's web administration interface is accessible from the WAN (external) network rather than only from the LAN. Check router firewall settings and port forwarding rules for open HTTP/HTTPS ports facing the internet.Affected if Remote management or the web interface is exposed to WAN, allowing external attackers to reach the vulnerable endpoint.
A user is affected if they are running the China Mobile An Lianbao WF-1 router with firmware version 1.0.1 and the vulnerable /api/ZRQos/set_online_client endpoint is accessible, particularly from external 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 dataIsolate affected devices behind a firewall to limit external attack surface; apply vendor firmware updates when available; if no patch exists, consider device replacement as the vendor may be unresponsive (CVE is from 2021).
- 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-25812 — 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-25812 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