dbcve.org
Archer Mr600 FirmwareOperating system · Tp Link

CVE-2025-14756

HIGH · 8.8 CVSS v3.1 Published 2026-01-26
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Command injection vulnerability was found in the admin interface component of TP-Link Archer MR600 v5 firmware, allowing authenticated attackers to execute system commands with a limited character length via crafted input in the browser developer console, possibly leading to service disruption or full compromise.

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

A command injection vulnerability exists in the admin web interface of TP-Link Archer MR600 v5 routers. Authenticated attackers can inject arbitrary system commands through crafted input via the browser developer console, despite a limited character length restriction. Successful exploitation allows execution of OS-level commands with the privileges of the admin interface, potentially leading to complete device compromise.

MitigationApply vendor-supplied firmware updates when available; until then, restrict administrative interface access to trusted networks only and monitor for unauthorized access attempts.

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
Archer Mr600 FirmwareOperating system
Affected:< 1.1.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 and hardware version
    Locate the device label on the router or access the admin web interface (typically at 192.168.0.1) and check the status page to confirm the exact model is TP-Link Archer MR600 v5
    Affected if The device is not an Archer MR600 v5 model - this vulnerability only applies to that specific hardware version
  2. Check installed firmware version
    Access the admin web interface, navigate to Settings > System > Firmware Upgrade or Status page, and record the displayed firmware version number
    Affected if The firmware version is less than 1.1.0 (for example, 1.0.0, 1.0.5, etc.) - versions below 1.1.0 are affected
  3. Verify admin interface accessibility
    Log into the admin web interface, go to Advanced > Network > Remote Management, and check if Remote Management from WAN is enabled and note the allowed IP range
    Affected if Remote Management from WAN is enabled and accessible from untrusted networks - this increases exposure to authenticated attackers
  4. Inspect web interface for console access
    Open browser developer tools (F12), switch to the Console tab, and verify if you can execute JavaScript commands while authenticated to the admin interface
    Affected if JavaScript command execution is possible in the browser console while logged into the admin panel - this confirms the attack surface exists

You are affected if you have a TP-Link Archer MR600 v5 router running firmware version 1.1.0 or lower and the admin interface is accessible (locally or remotely) to untrusted users.

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.1.0 or later
Fixed in 1.1.0
Interim mitigation

Apply vendor-supplied firmware updates when available; until then, restrict administrative interface access to trusted networks only and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

TP-Link Archer MR600 Firmware version 1.1.0 or later

  1. Log into the TP-Link Archer MR600 admin interface at the router's local IP address (typically 192.168.0.1 or 192.168.1.1)
  2. Navigate to System > Firmware Upgrade or Advanced > Firmware Upgrade
  3. Check the current firmware version under Device Info or Status
  4. Download the latest firmware version 1.1.0 or later from the official TP-Link support page: https://www.tp-link.com/support/download/archer-mr600/
  5. Click the Upgrade button and select the downloaded firmware file
  6. Wait for the upload and installation to complete - do not power off the router
  7. After reboot, log back into the admin interface and verify the firmware version shows 1.1.0 or later
  8. As an authenticated command injection was possible, change the administrator password to a strong, unique password
Caveat Review TP-Link's firmware release notes for the 1.1.0 update for any configuration reset requirements or known compatibility issues before upgrading

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

Fix this in Archer Mr600 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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