CVE-2026-35904
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 · uneditedIncorrect access control in the web management interface of T3 Technology CPE models T625Pro v1.0.07, T6825G v1.0.03, and T7281 v1.0.03 allows unauthorized attackers to enable the Telnet service via sending a crafted request to a vulnerable CGI component.
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 confidenceIncorrect access control in the web management interface of T3 Technology CPE devices allows unauthenticated attackers to enable the Telnet service by sending a crafted request to a vulnerable CGI component. This provides remote shell access to the device without proper authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 modelCheck the CPE device model through device label, web interface footer, or SNMP/sysinfo query. Affected models are T625Pro, T6825G, and T7281.Affected if The device model is T625Pro, T6825G, or T7281 and the web management interface is accessible.
-
Verify Telnet service statusCheck if Telnet service (port 23) is listening on the device using 'netstat -an | grep :23' or by scanning the device from an authorized management IP.Affected if Telnet service is unexpectedly enabled and listening on the device when it was not intentionally configured.
-
Inspect web management interface exposureDetermine if the CGI component of the web management interface is exposed to untrusted networks. Check router/fouter ACLs and firewall rules for inbound access to HTTP/HTTPS ports (80/443) from external IPs.Affected if The web management interface CGI endpoint is reachable from untrusted networks without IP restrictions.
-
Review authentication configurationCheck the web management interface settings to confirm whether authentication is required for all functions, particularly the service enablement features.Affected if The CGI component permits unauthenticated access to privileged functions like Telnet service activation.
-
Analyze logs for exploitation indicatorsSearch web server and system logs for unusual POST requests to CGI endpoints, especially those targeting service configuration paths, and for Telnet service enablement events.Affected if Logs show unauthorized CGI requests or Telnet service activation events that were not initiated by legitimate administrators.
A user is affected if they operate a T625Pro, T6825G, or T7281 CPE device with the web management interface exposed to untrusted networks and Telnet service is enabled without administrator authorization.
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 updates if available; otherwise, disable remote web management access via firewall rules and implement network segmentation to minimize exposure of the management interface to untrusted networks.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35904 — 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-2026-35904 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