dbcve.org
Tl Wr820n FirmwareOperating system · Tp Link

CVE-2025-14175

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-29
Fix available
A fix is available. Upgrade to 1.15.0 or later.
See remediation →
70/100
Remediation priority · Elevated
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 in the SSH server of TP-Link TL-WR820N v2.80 allows the use of a weak cryptographic algorithm, enabling an adjacent attacker to intercept and decrypt SSH traffic. Exploitation may expose sensitive information and compromise confidentiality.

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 confidence

The SSH server implementation in TP-Link TL-WR820N v2.80 uses weak cryptographic algorithms, allowing an adjacent network attacker to intercept and decrypt SSH sessions. This likely involves use of deprecated ciphers (e.g., CBC mode), weak key exchange algorithms, or outdated encryption schemes that are vulnerable to cryptanalysis.

MitigationApply available firmware updates from TP-Link for the TL-WR820N; if no update exists, disable the SSH service if not required, or implement network segmentation to restrict adjacent access.

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 Wr820n FirmwareOperating system
Affected:< 1.15.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

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

  1. Confirm device model is TP-Link TL-WR820N
    Log into the router web interface or check the device label to verify the exact model number
    Affected if The device is a TP-Link TL-WR820N unit
  2. Check installed firmware version
    Access the router web interface, navigate to Status or System settings, and record the firmware version displayed
    Affected if The firmware version is lower than 1.15.0 (e.g., v2.80 as mentioned in CVE)
  3. Verify SSH service is enabled
    Attempt to connect to the router on TCP port 22 using an SSH client, or check the router web interface under Security or Administration settings for an SSH enable option
    Affected if SSH responds on port 22 and accepts connections
  4. Check SSH protocol and cipher configuration
    Connect via SSH and run 'sshd -T' if accessible, or use 'nmap --script ssh2-enum-algos -p 22 <router-ip>' from a connected host to list supported algorithms
    Affected if The SSH service offers deprecated CBC mode ciphers, weak key exchange algorithms (e.g., diffie-hellman-group1-sha1), or other outdated encryption schemes

You are affected if you have a TL-WR820N router running firmware version below 1.15.0 with SSH service enabled and the server offers weak cryptographic algorithms.

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
Upgrade available Upgrade to 1.15.0 or later
Fixed in 1.15.0
Interim mitigation

Apply available firmware updates from TP-Link for the TL-WR820N; if no update exists, disable the SSH service if not required, or implement network segmentation to restrict adjacent access.

Recommended fix Moderate confidence

TL-WR820N firmware 1.15.0

  1. Obtain firmware version 1.15.0 or later from the official TP-Link support website (www.tp-link.com)
  2. Access the TL-WR820N router's web-based management interface
  3. Navigate to the System or Administration section containing firmware upgrade options
  4. Upload and install the firmware version 1.15.0 or newer
  5. Allow the router to complete the firmware installation and automatic reboot
  6. Verify the installed firmware version matches the patched release
Caveat Firmware updates may temporarily disrupt network connectivity; ensure stable power during the upgrade process

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

Fix this in Tl Wr820n Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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