CVE-2025-26711
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 · uneditedThere is an unauthorized access vulnerability in ZTE T5400. Due to improper permission control of the Web module interface, an unauthorized attacker can obtain sensitive information through the interface.
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 confidenceZTE T5400 contains an improper permission control vulnerability in its Web module interface. An unauthenticated attacker can exploit this authorization flaw to access sensitive information that should be restricted to authorized users only, due to missing or inadequate access control checks on certain web interface endpoints.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/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.
-
Confirm ZTE T5400 is in useIdentify the device or software product. Check the system information, banner, or administrative interface to verify the product name is ZTE T5400.Affected if The system is running ZTE T5400 firmware.
-
Verify Web module is accessibleDetermine if the Web management interface is exposed by attempting to access the HTTP/HTTPS ports on the device. Check network configuration to see if the Web interface is reachable remotely or locally.Affected if The Web module interface is accessible on the network.
-
Test unauthenticated endpoint accessUse a browser or HTTP client (such as curl) to request common Web interface paths without providing any authentication credentials. Typical endpoints to probe include /, /admin, /status, /config, /api/, or any page that typically requires login. Observe whether the server returns sensitive data, configuration pages, or administrative information without redirecting to a login page.Affected if The Web interface returns sensitive content, configuration data, or administrative pages without requiring any authentication.
-
Inspect HTTP response behaviorCapture and analyze HTTP responses from the Web interface. Compare responses when sending unauthenticated requests versus authenticated ones. Look for status codes (200 vs 302/401), session tokens, or data exposure in the response body.Affected if The server grants access to protected resources or returns 200 OK responses with sensitive data when no credentials are provided.
-
Check for missing authorization headersReview the HTTP requests and responses when accessing the Web interface. Examine whether endpoints enforce authorization by checking for proper session validation, role checks, or privilege verification before returning data.Affected if Endpoints return requested data regardless of whether valid authentication headers or session cookies are included in the request.
The environment is affected if ZTE T5400 is running and its Web module interface allows unauthenticated access to sensitive information or administrative endpoints.
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 dataImplement proper authentication and authorization checks on all Web module interfaces to enforce role-based access controls. Verify that sensitive endpoints require valid authentication and appropriate privileges before returning any data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26711 — 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-26711 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