dbcve.org
Archer C60 FirmwareOperating system · Tp Link

CVE-2026-1571

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 260206 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
User-controlled input is reflected into the HTML output without proper encoding on TP-Link Archer C60 v3, allowing arbitrary JavaScript execution via a crafted URL. An attacker could run script in the device web UI context, potentially enabling credential theft, session hijacking, or unintended actions if a privileged user is targeted.

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 reflected cross-site scripting (XSS) vulnerability exists in the TP-Link Archer C60 v3 router web interface. User-supplied input is returned in the HTTP response without HTML encoding, allowing an attacker to inject arbitrary JavaScript that executes in the context of the router's web UI when a victim clicks a crafted link.

MitigationApply the vendor-supplied firmware update when available. As a temporary workaround, avoid clicking untrusted links to the router's admin interface.

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 C60 FirmwareOperating system
Affected:< 260206

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify device model
    Access the router web interface or check the device label to confirm it is an Archer C60 v3 hardware version
    Affected if Device is not an Archer C60 v3, then not affected
  2. Check firmware version
    Log into the router web interface and navigate to Status or System > Firmware Upgrade page to view the current firmware version, or use the command 'archer-c60v3-webupgrade' if SSH/telnet is enabled
    Affected if Firmware version is less than 260206 (e.g., 260205, older versions)
  3. Verify web interface is accessible
    Confirm the router's HTTP/HTTPS management interface is reachable on the local network
    Affected if Web interface is enabled (default state for this router)
  4. Confirm firmware version format
    Compare your installed version number against the affected range - versions are typically displayed as a build date code like '260206'
    Affected if Version string shows a number lower than 260206

You are affected if you are running a TP-Link Archer C60 v3 with firmware version below 260206 and the router's web interface is accessible.

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 260206 or later
Fixed in 260206
Interim mitigation

Apply the vendor-supplied firmware update when available. As a temporary workaround, avoid clicking untrusted links to the router's admin interface.

Recommended fix High confidence

Firmware version 260206 or later for TP-Link Archer C60

  1. Navigate to the TP-Link Archer C60 web management interface by entering the router's IP address in a web browser
  2. Log in with administrator credentials
  3. Go to System > Firmware Upgrade (or similar menu path)
  4. Download the firmware version 260206 or later from the official TP-Link support website (www.tp-link.com)
  5. In the web interface, locate the firmware upgrade section and click 'Browse' or 'Choose File' to select the downloaded firmware file
  6. Click 'Upgrade' or 'Update' to begin the firmware update process
  7. Wait for the upgrade to complete - do not power off or restart the router during this process
  8. After the upgrade completes, the router will automatically reboot

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

Fix this in Archer C60 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,460
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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