CVE-2025-26009
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 has an Information Disclosure vulnerability when requesting systemutilit.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 confidenceThe Telesquare TLR-2005KSH router version 1.1.4 contains an information disclosure vulnerability in the systemutilit.cgi endpoint. An unauthenticated attacker could potentially access sensitive system information by requesting this CGI script, which may expose configuration details, credentials, or operational data.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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's 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 router, then this CVE does not apply
-
Check the installed firmware versionLog into the router web interface and navigate to the firmware/version information page, or use the command line if available, to determine the exact firmware versionAffected if The firmware version is NOT 1.1.4, then this specific CVE does not apply (different versions may have other issues)
-
Verify the systemutilit.cgi endpoint existsSend an HTTP GET request to http://<router-ip>/cgi-bin/systemutilit.cgi (or the equivalent path on your device) using curl or a browserAffected if The endpoint returns a 404 error or is not found, the device may not be vulnerable to this specific issue
-
Confirm the endpoint is accessible without authenticationAttempt to access the systemutilit.cgi endpoint from a browser or curl without providing any login credentialsAffected if The endpoint returns sensitive system information, configuration details, or operational data without requiring authentication, you are affected by this vulnerability
You are affected if you have a Telesquare TLR-2005KSH router running firmware version 1.1.4 and the systemutilit.cgi endpoint returns sensitive information without requiring authentication.
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 dataRestrict or disable access to the systemutilit.cgi endpoint through firewall rules or web server configuration until an official firmware patch is available from Telesquare; if the device is exposed to untrusted networks, isolate it behind a controlled network boundary.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26009 — 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-26009 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