CVE-2025-14586
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 determined in TOTOLINK X5000R 9.1.0cu.2089_B20211224. Affected by this issue is the function snprintf of the file /cgi-bin/cstecgi.cgi?action=exportOvpn&type=user. This manipulation of the argument User causes os command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
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 confidenceThe TOTOLINK X5000R router firmware 9.1.0cu.2089_B20211224 contains an OS command injection vulnerability in the CGI binary at /cgi-bin/cstecgi.cgi. The 'exportOvpn' action with 'user' type passes the User parameter unsanitized to snprintf, allowing remote attackers to inject arbitrary OS commands via the User argument.
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.2089_b20211224CVSS 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 interface or check the device label to confirm it is a TOTOLINK X5000R modelAffected if Device is not a TOTOLINK X5000R router - different models are not affected by this specific CVE
-
Check firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the current firmware version, or use command: cat /proc/firmware_version if you have telnet/ssh accessAffected if Firmware version is exactly 9.1.0cu.2089_b20211224 - this is the only affected version per the CVE
-
Verify CGI binary existsAttempt to access the CGI endpoint at /cgi-bin/cstecgi.cgi via HTTP (e.g., curl http://<router-ip>/cgi-bin/cstecgi.cgi) - a 404 or error response confirms the binary existsAffected if The CGI binary /cgi-bin/cstecgi.cgi is present on the device - this is required for exploitation
-
Confirm remote access is enabledCheck router firewall settings to determine if the web interface (port 80/443) is accessible from untrusted networks or the WAN interfaceAffected if Remote administration is enabled and the web interface is reachable from external networks - this is required for remote exploitation
You are affected only if you have a TOTOLINK X5000R router running firmware version 9.1.0cu.2089_b20211224 with the CGI web interface accessible to the 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-supplied firmware patch when available; as an interim control, disable remote administration access to the router's web interface or restrict it to trusted IPs via firewall rules.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14586 — 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-14586 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