CVE-2025-26010
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 allows unauthorized password modification when requesting the admin.cgi parameter with setUserNamePassword.
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 confidenceThe Telesquare TLR-2005KSH router version 1.1.4 contains a critical authentication bypass vulnerability in admin.cgi that allows unauthenticated remote attackers to modify the administrator password by sending a specially crafted request with the setUserNamePassword parameter, effectively granting full administrative access to the device.
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 the device label/marketing to confirm it is a Telesquare TLR-2005KSH routerAffected if The device is not a Telesquare TLR-2005KSH, then it is not affected by this specific CVE
-
Determine the firmware versionLog into the router admin interface and navigate to the status or system information page to view the installed firmware version, or use the command line to check /proc/version or similar if telnet/ssh access is availableAffected if The firmware version is exactly 1.1.4; other versions are not affected by this specific CVE
-
Verify admin.cgi is accessibleAttempt to access the admin.cgi page from the web interface or test for its presence via HTTP request to http://[device-ip]/admin.cgiAffected if The admin.cgi script exists and is reachable without authentication, indicating the vulnerable endpoint is present
-
Check if remote administration is enabledIn the router web interface, navigate to the administration or remote management settings to see if remote administrative access is enabledAffected if Remote administration is enabled, allowing unauthenticated attackers to reach the vulnerable admin.cgi endpoint from the network
You are affected if you are running a Telesquare TLR-2005KSH router with firmware version 1.1.4 and the admin.cgi interface is accessible, especially if remote administration is enabled.
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 dataImmediately restrict network access to the device's administrative interface, disable remote administration if possible, and monitor for unauthorized configuration changes. If vendor firmware update is unavailable, consider replacing the device with a supported model.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26010 — 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-26010 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