CVE-2026-1740
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 · uneditedA vulnerability was found in EFM ipTIME A8004T 14.18.2. This impacts the function httpcon_check_session_url of the file /cgi/timepro.cgi of the component Hidden Hiddenloginsetup Interface. The manipulation results in improper authentication. The attack may be performed from remote. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceAuthentication bypass vulnerability in the hidden loginsetup interface of EFM ipTIME A8004T router firmware v14.18.2. The httpcon_check_session_url function in /cgi/timepro.cgi improperly validates session URLs, allowing remote attackers to bypass authentication and access the management interface without credentials.
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= 14.18.2CVSS 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.
-
Confirm router model is A8004TAccess the router web interface and navigate to the status or system information page, or physically inspect the device label. Verify the model number displays as EFM ipTIME A8004T.Affected if Device is not an EFM ipTIME A8004T router
-
Identify installed firmware versionLog into the router admin panel and locate the firmware version in the system status or firmware upgrade section. Compare the displayed version number to 14.18.2.Affected if Firmware version is exactly 14.18.2
-
Test access to timepro.cgi endpointFrom a client on the same network, attempt an HTTP request to the router at /cgi/timepro.cgi with the loginsetup parameter, such as http://[router-ip]/cgi/timepro.cgi?menu=loginsetup. Observe whether the page loads without requiring authentication credentials.Affected if The loginsetup or hidden login interface responds without authentication
-
Check WAN/remote management exposureIn the router admin panel, examine the firewall or remote management settings. Look for options labeled WAN access, remote management, or external access. Determine if the management interface is reachable from the internet.Affected if Remote WAN access to the management interface is enabled
Environment is affected if the device is an ipTIME A8004T running firmware version 14.18.2, the hidden loginsetup interface in timepro.cgi is accessible without credentials, and the management interface is exposed to WAN.
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 dataSince the vendor did not respond to disclosure and no patch is available, immediately restrict access to the device's management interface via network segmentation or firewall rules—disable remote WAN access if enabled. Consider replacing affected devices with models receiving active security support.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1740 — 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-1740 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