CVE-2025-26005
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 · uneditedTelesquare TLR-2005KSH 1.1.4 is vulnerable to unauthorized stack overflow vulnerability when requesting admin.cgi parameter with setNtp.
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 confidenceA critical stack-based buffer overflow vulnerability exists in Telesquare TLR-2005KSH firmware version 1.1.4. The vulnerability is triggered via an unauthenticated HTTP request to the admin.cgi endpoint with the setNtp parameter, allowing remote attackers to overflow the stack and potentially achieve remote code execution.
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= 1.1.4CVSS 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 the device modelAccess the router web interface or check network device information. Look for 'TLR-2005KSH' or 'Telesquare' branding on the login page, or use network scanning to fingerprint the device.Affected if The device is a Telesquare TLR-2005KSH router
-
Determine the firmware versionCheck the router admin interface for a firmware version display (typically in Status, System, or About sections), or query the device via SNMP or API if available.Affected if The firmware version is exactly 1.1.4
-
Verify the admin.cgi endpoint existsAttempt to access the admin.cgi endpoint on the router (e.g., http://<router-ip>/admin.cgi or /cgi-bin/admin.cgi).Affected if The admin.cgi endpoint is present and responds to requests
-
Check network exposure of admin interfaceScan the router's IP for open HTTP/HTTPS ports (80, 443, 8080, 8443) from external networks. Verify if the web administration interface is accessible from untrusted networks.Affected if The admin interface is reachable from untrusted/untrusted networks (not just LAN or trusted IPs)
-
Confirm setNtp parameter handling existsIf authenticated (or using the vulnerability without auth), probe for the setNtp parameter in admin.cgi. This may be visible in NTP settings page or by inspecting form submissions.Affected if The router processes NTP settings through admin.cgi with a setNtp parameter
If the device is a Telesquare TLR-2005KSH running firmware 1.1.4 and the admin.cgi web interface is network-accessible, the environment is affected by CVE-2025-26005.
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 update when available; until then, isolate the affected device behind a firewall and disable external administrative access to mitigate exploitation.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26005 — 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-26005 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