dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7721

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A security vulnerability has been detected in Totolink WA300 5.2cu.7112_B20190227. This affects the function NTPSyncWithHost of the file /cgi-bin/cstecgi.cgi. Such manipulation of the argument hostTime leads to command injection. The attack can be executed remotely. The exploit has been disclosed publicly and may be used.

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 confidence

Command injection vulnerability in Totolink WA300 router firmware (5.2cu.7112_B20190227) where the NTPSyncWithHost function in /cgi-bin/cstecgi.cgi does not sanitize the hostTime parameter, allowing remote authenticated attackers to inject and execute arbitrary shell commands on the device.

MitigationApply vendor firmware update if available; otherwise restrict access to the CGI management interface via network ACLs or firewall rules, or disable the NTP synchronization feature if possible.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 the device model
    Access the router web interface or check the device label/menu to confirm the model is Totolink WA300
    Affected if The device is not a Totolink WA300 router, then it is not affected by this specific CVE
  2. Check the firmware version
    Log into the router administration panel and navigate to the firmware/version information section, or use the router's status page to display the current firmware build
    Affected if The installed firmware version matches or precedes 5.2cu.7112_B20190227 (or any earlier 5.2cu.7112 series build)
  3. Verify the CGI endpoint is accessible
    Attempt to access the URI /cgi-bin/cstecgi.cgi on the router (typically via http://router-ip/cgi-bin/cstecgi.cgi)
    Affected if The endpoint responds (indicating the web interface is active and the CGI binary exists)
  4. Confirm NTP synchronization feature is enabled
    In the router web UI, locate the NTP or time synchronization settings (usually under System or Time settings) and verify the feature is turned on
    Affected if NTP synchronization is enabled and configured to accept a host time parameter

The device is affected if it is a Totolink WA300 running firmware at or before 5.2cu.7112_B20190227, the CGI interface is accessible, and the NTP synchronization feature is enabled with user-controllable hostTime input.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update if available; otherwise restrict access to the CGI management interface via network ACLs or firewall rules, or disable the NTP synchronization feature if possible.

Recommended fix Moderate confidence

Latest available WA300 firmware from Totolink's official support page (www.totolink.net)

  1. 1. Identify the current firmware version of the Totolink WA300 device by accessing the web management interface or checking the device label.
  2. 2. Navigate to the official Totolink support page at www.totolink.net and locate the WA300 product downloads section.
  3. 3. Download the latest available firmware version for the WA300 device.
  4. 4. Access the device's web administration panel and locate the firmware upgrade or system settings section.
  5. 5. Upload and apply the latest firmware version following the vendor's upgrade instructions.
  6. 6. After the upgrade completes, verify the device is functioning properly and confirm the new firmware version.
  7. 7. Ensure the NTPSyncWithHost function (or NTP settings) is no longer vulnerable to command injection by testing with invalid input.
Caveat Review release notes for any configuration or feature changes before upgrading; backup current device configuration if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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