dbcve.org
Tl Wr845n FirmwareOperating system · Tp Link

CVE-2024-57040

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-26
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
TP-Link TL-WR845N devices with firmware TL-WR845N(UN)_V4_200909 and TL-WR845N(UN)_V4_190219 was discovered to contain a hardcoded password for the root account which can be obtained by analyzing downloaded firmware or via a brute force attack through physical access to the router. NOTE: The supplier has stated that this issue was fixed in firmware versions 250401 or later.

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

The TP-Link TL-WR845N router contains a hardcoded password for the root account that can be extracted by analyzing the firmware binary or discovered through brute force attacks with physical access to the device. This gives attackers full administrative control over the router.

MitigationUpdate the router firmware to version 250401 or later to replace the vulnerable firmware containing the hardcoded 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
Tl Wr845n FirmwareOperating system
Affected:= 190219= 200909= 201214

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 the router firmware version
    Access the router's web administration interface and navigate to the Status or System section to view the firmware version. Alternatively, check the label on the router device itself for the firmware version printed there.
    Affected if The displayed firmware version matches exactly 190219, 200909, or 201214
  2. Confirm the device model
    Verify that the router is specifically a TP-Link TL-WR845N model. Check the product label on the device or the web interface status page for the exact model number.
    Affected if The device model is TL-WR845N and the firmware version is one of the three affected versions listed
  3. Check for hardcoded root password presence
    If you have access to the router firmware file (either extracted from the device or downloaded from TP-Link), examine the firmware binary or configuration files for hardcoded password strings. Look for the root user account password embedded in the firmware image.
    Affected if A hardcoded password string is found associated with the root account in the firmware
  4. Verify root access method
    Attempt to access the router via console/Telnet/SSH if available, or analyze the firmware to determine if the root account can be accessed without authentication using a known hardcoded credential.
    Affected if The root account is accessible using a hardcoded password without requiring legitimate administrator credentials

The device is affected if it is a TP-Link TL-WR845N running firmware version 190219, 200909, or 201214 and contains the hardcoded root password vulnerability.

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

Update the router firmware to version 250401 or later to replace the vulnerable firmware containing the hardcoded credentials.

Recommended fix High confidence

TL-WR845N firmware version 250401 or later

  1. 1. Download the latest firmware version 250401 or later for the TP-Link TL-WR845N from TP-Link's official support website (support.tp-link.com)
  2. 2. Access the router's web management interface by entering the router's IP address in a web browser
  3. 3. Log in with administrator credentials
  4. 4. Navigate to the System Tools > Firmware Upgrade (or similar) section
  5. 5. Click on the upgrade option and select the downloaded firmware file
  6. 6. Wait for the firmware upload and installation to complete - do not power off the router during this process
  7. 7. After the router restarts, log in again and verify the firmware version has been updated

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

Fix this in Tl Wr845n Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57040 — 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-2024-57040 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