CVE-2026-5176
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 · uneditedA security flaw has been discovered in Totolink A3300R 17.0.0cu.557_b20221024. Affected is the function setSyslogCfg of the file /cgi-bin/cstecgi.cgi. Performing a manipulation of the argument provided results in command injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks.
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 confidenceA command injection vulnerability exists in Totolink A3300R router firmware 17.0.0cu.557_b20221024 within the setSyslogCfg function of /cgi-bin/cstecgi.cgi. The function fails to properly sanitize user input, allowing an attacker to inject and execute arbitrary operating system commands remotely.
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= 17.0.0cu.557_b20221024CVSS 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.
-
Confirm device model is Totolink A3300RAccess the router web interface and check the device model information, or check the device label. Alternatively, inspect the HTTP responses from the router which may reveal the model in headers or login pages.Affected if The device is not a Totolink A3300R router - this vulnerability does not apply to other models.
-
Identify the installed firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the footer or status page of the web interface for version information.Affected if The installed firmware version is exactly 17.0.0cu.557_b20221024 - this is the only version listed as affected by this CVE.
-
Check if /cgi-bin/cstecgi.cgi is present and accessibleAttempt to access https://<router-ip>/cgi-bin/cstecgi.cgi via HTTP OPTIONS request or by analyzing available CGI endpoints on the device. This file contains the vulnerable setSyslogCfg function.Affected if The CGI binary exists and responds to requests - the vulnerable function is present in this version.
-
Verify the setSyslogCfg function is exposedSend a crafted request to the CGI endpoint with the setSyslogCfg action parameter to confirm the function exists. This typically involves a POST request with the function name.Affected if The function responds without error - the command injection point is available for exploitation.
You are affected if you are running a Totolink A3300R router with firmware version 17.0.0cu.557_b20221024 and the web interface is accessible to an attacker.
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 dataApply vendor firmware patch if available; otherwise disable remote management interfaces, implement network segmentation, or replace affected devices. If continued use is required, restrict access to the management interface via firewall rules.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5176 — 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-2026-5176 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