CVE-2026-1547
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 vulnerability was detected in Totolink A7000R 4.1cu.4154. This affects the function setUnloadUserData of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument plugin_name results in command injection. It is possible to launch the attack remotely. The exploit is now public 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 confidenceCommand injection vulnerability in Totolink A7000R router firmware 4.1cu.4154 allows remote attackers to execute arbitrary OS commands via the plugin_name parameter passed to the setUnloadUserData function in /cgi-bin/cstecgi.cgi. The lack of input sanitization on this parameter enables attackers to inject shell metacharacters into system commands.
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= 4.1cu.4154CVSS 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 model and firmware versionAccess the router web interface (typically 192.168.0.1 or 192.168.1.1) and navigate to Status or System Info page to view the hardware model and firmware version. Alternatively, check the label on the device or use Nmap to fingerprint the device.Affected if The device model shows Totolink A7000R with firmware version 4.1cu.4154 exactly.
-
Verify vulnerable CGI endpoint existsAttempt to access the file /cgi-bin/cstecgi.cgi via HTTP/HTTPS request to the router. If the file is present and responds, the endpoint is exposed. Use curl or a browser to test: curl http://<router-ip>/cgi-bin/cstecgi.cgiAffected if The /cgi-bin/cstecgi.cgi endpoint responds with any HTTP status other than 404.
-
Check web interface exposure to untrusted networksReview router firewall settings to determine if the HTTP/HTTPS management ports (80/443) are bound to WAN or an untrusted interface. Check if remote management is enabled in the administration settings.Affected if The web management interface is accessible from WAN or an untrusted network segment.
-
Verify command injection is possibleSend a crafted POST request to /cgi-bin/cstecgi.cgi with the setUnloadUserData action and a test payload in the plugin_name parameter, such as plugin_name=`whoami`. Monitor for command execution in the response or network behavior.Affected if The plugin_name parameter executes injected shell commands and returns the output.
The device is affected only if it is a Totolink A7000R running exactly firmware version 4.1cu.4154 AND the cstecgi.cgi endpoint is accessible from an untrusted network.
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 restrict network access to the web management interface (port 80/443) using firewall rules or VLAN segmentation to prevent unauthorized external access to the CGI interface.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1547 — 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-1547 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