CVE-2025-29064
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 · uneditedAn issue in TOTOLINK x18 v.9.1.0cu.2024_B20220329 allows a remote attacker to execute arbitrary code via the sub_410E54 function of the cstecgi.cgi.
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 confidencePre-authentication command injection vulnerability in TOTOLINK x18 router firmware v9.1.0cu.2024_B20220329. The cstecgi.cgi web interface contains a flaw in the sub_410E54 function that fails to sanitize user input before passing it to system shell commands, enabling remote attackers to execute arbitrary code without authentication. CVSS 9.8 indicates trivial network exploitability.
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= 9.1.0cu.2024_b20220329CVSS 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 TOTOLINK X18 router modelLog into the router admin interface and navigate to System Status or Device Information page to confirm the model is X18. Alternatively, check the device label or packaging.Affected if Device model is NOT TOTOLINK X18 - the vulnerability does not apply to other models
-
Check installed firmware versionIn the router admin interface, go to System Management > Firmware Upgrade or System Status page. Locate the firmware version field. Compare it to the affected version: 9.1.0cu.2024_B20220329Affected if Firmware version is exactly 9.1.0cu.2024_B20220329 - this is the only confirmed affected version
-
Verify cstecgi.cgi is accessibleFrom a system on the same network, attempt to access http://[router-ip]/cstecgi.cgi via HTTP GET or POST request. Use curl or similar tool: curl -v http://[router-ip]/cstecgi.cgiAffected if The CGI endpoint responds or accepts requests - indicates the vulnerable web interface is active
-
Check if remote management is exposed to WANAccess router firewall or access control settings. Determine if the web interface (port 80/443) is bound to WAN interface or has any port forwarding rules exposing cstecgi.cgi to the internet. Check router WAN access settings under Security or Access Control.Affected if WAN interface has HTTP/HTTPS management enabled or port forwarding exposes the admin interface to external networks - increases exposure to remote attack
User is affected if they own a TOTOLINK X18 router running firmware version 9.1.0cu.2024_B20220329 AND the cstecgi.cgi web interface is network-accessible (especially from WAN).
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 dataIf vendor firmware update unavailable, immediately disable remote management access from WAN and restrict admin interface to trusted networks only via firewall rules. Consider device replacement if end-of-life.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29064 — 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-2025-29064 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