dbcve.org
Archer Be450 FirmwareOperating system · Tp Link

CVE-2026-5509

HIGH · 7.2 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
78/100
Remediation priority · High
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
An authenticated command injection vulnerability exists in the Archer BE450 v1 and BE7200 v1 router that allows an administrator to execute arbitrary system commands through the web management interface. After successfully authenticating to the admin interface, an attacker can leverage the browser’s developer console by supplying a crafted input that is passed to backend system commands without adequate sanitization. Successful exploitation enables execution of arbitrary commands with elevated privileges on the device, which may allow the attacker to start unauthorized services, modify system configuration, or otherwise fully compromise the router’s operating environment.

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

This is an authenticated command injection vulnerability in TP-Link Archer BE450 and BE7200 routers. An authenticated administrator can execute arbitrary OS commands through the web management interface by supplying crafted input via the browser developer console, which is passed to backend system calls without proper sanitization, resulting in elevated privileges on the device.

MitigationApply the vendor-provided firmware patch when available. Until then, limit administrative access to trusted users only, disable remote management if possible, and monitor for unauthorized administrative sessions.

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 Be450 FirmwareOperating system
Affected:< 1.3.0
Archer Be7200 FirmwareOperating system
Affected:< 1.3.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 router model
    Log into the router web management interface (typically at 192.168.0.1 or 192.168.1.1) and locate the device model information, usually found under System, Status, or Device Info sections
    Affected if The router model is TP-Link Archer BE450 or Archer BE7200
  2. Check installed firmware version
    In the router web interface, navigate to the firmware version display (usually under System > Firmware Upgrade, Status, or Device Info) and note the exact firmware version number displayed
    Affected if The displayed firmware version is below 1.3.0 (for example, 1.2.5, 1.0.8, etc.)
  3. Confirm vulnerability applicability
    Verify that the web management interface is accessible and that you have administrator credentials. The vulnerability requires an authenticated admin session to exploit.
    Affected if The device is a BE450 or BE7200 running firmware version 1.3.0 or higher - you are NOT affected. If version is below 1.3.0, you ARE affected.

You are affected if your TP-Link Archer BE450 or BE7200 router is running firmware version lower than 1.3.0.

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.3.0 or later
Fixed in 1.3.0
Interim mitigation

Apply the vendor-provided firmware patch when available. Until then, limit administrative access to trusted users only, disable remote management if possible, and monitor for unauthorized administrative sessions.

Recommended fix High confidence

Archer BE450 and BE7200 Firmware version 1.3.0 or later

  1. Access the TP-Link Archer BE450 or BE7200 router web management interface
  2. Navigate to the Firmware Upgrade section (usually under System or Administration settings)
  3. Download the latest firmware version 1.3.0 or later from the official TP-Link support website (www.tp-link.com)
  4. Upload the firmware file through the web interface and wait for the upgrade process to complete
  5. After reboot, verify the firmware version is 1.3.0 or higher in the system information page
  6. Re-authenticate to confirm the vulnerability is remediated

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

Fix this in Archer Be450 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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