dbcve.org
Ex1800t FirmwareOperating system · Totolink

CVE-2025-1852

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been found in Totolink EX1800T 9.1.0cu.2112_B20220316 and classified as critical. This vulnerability affects the function loginAuth of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument password leads to buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

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 · high confidence

A buffer overflow vulnerability exists in the loginAuth function of Totolink EX1800T router firmware (version 9.1.0cu.2112_B20220316). The vulnerability is triggered via a crafted password argument to the /cgi-bin/cstecgi.cgi endpoint, allowing remote attackers to execute arbitrary code with critical severity (CVSS 9.8).

MitigationIf a vendor firmware update is available, apply it immediately. If no patch exists, implement network-level mitigations such as restricting access to the management interface via firewall rules or VLAN segmentation, and disable remote administration if not required.

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
Ex1800t FirmwareOperating system
Affected:= 9.1.0cu.2112_b20220316

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router web interface or check the device label to confirm it is a Totolink EX1800T router
    Affected if The device is NOT a Totolink EX1800T model - different models are not affected by this specific CVE
  2. Check firmware version
    Navigate to the router admin panel (typically at 192.168.0.1 or 192.168.1.1), look in System Settings or Firmware Upgrade section for the current firmware version, or use the command 'cat /proc/version' if SSH/Telnet access is available
    Affected if Firmware version is exactly 9.1.0cu.2112_b20220316 - only this exact version is listed as affected
  3. Verify cstecgi.cgi endpoint is accessible
    Attempt to access http://<router-ip>/cgi-bin/cstecgi.cgi from a browser or use curl to send a request to this endpoint
    Affected if The endpoint responds or accepts requests - this is the vulnerable service that must be exposed for exploitation
  4. Check if remote management is enabled
    In the router admin panel, look for Remote Management, Remote Access, or Administration settings - verify whether access to the web interface is allowed from WAN (external) networks
    Affected if Remote management from WAN is enabled - this exposes the vulnerable loginAuth function to external attackers

You are affected if you have a Totolink EX1800T router running firmware version 9.1.0cu.2112_b20220316 AND the /cgi-bin/cstecgi.cgi endpoint is accessible from the network where attackers could reach it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If a vendor firmware update is available, apply it immediately. If no patch exists, implement network-level mitigations such as restricting access to the management interface via firewall rules or VLAN segmentation, and disable remote administration if not required.

Recommended fix Moderate confidence

Latest firmware version available on www.totolink.net for EX1800T (verify version is newer than 9.1.0cu.2112_B20220316)

  1. 1. Visit the official Totolink support website at www.totolink.net and navigate to the EX1800T product page.
  2. 2. Download the latest available firmware version for the EX1800T device.
  3. 3. Access the device administration panel through a secure, trusted network connection.
  4. 4. Navigate to the firmware upgrade section in the device settings.
  5. 5. Upload and apply the latest firmware version, ensuring uninterrupted power during the upgrade process.
  6. 6. After the device restarts, verify the new firmware version is installed correctly.
  7. 7. Change administrative credentials, as the vulnerability affected the password handling in the login function.
Caveat Review release notes for any functionality changes or reset requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ex1800t Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1852 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1852 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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