dbcve.org
Tl Wr802n FirmwareOperating system · Tp Link

CVE-2026-3227

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 260303 / 260304 or later.
See remediation →
70/100
Remediation priority · Elevated
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 command injection vulnerability was identified in TP-Link TL-WR802N v4, TL-WR841N v14, and TL-WR840N v6 due to improper neutralization of special elements used in an OS command. In the router configuration import function allows an authenticated attacker to upload a crafted configuration file that results in execution of OS commands with root privileges during port-trigger processing. Successful exploitation allows an authenticated attacker to execute system commands with root privileges, leading to full device 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

Command injection vulnerability in TP-Link TL-WR802N v4, TL-WR841N v14, and TL-WR840N v6 routers allows authenticated attackers to upload crafted configuration files that execute OS commands with root privileges during port-trigger processing, leading to full device compromise.

MitigationApply vendor firmware updates when available, restrict administrative access to trusted users only, and consider network segmentation to limit exposure to the configuration import function.

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 Wr802n FirmwareOperating system
Affected:< 260304
Tl Wr841n FirmwareOperating system
Affected:< 260303
Tl Wr840n FirmwareOperating system
Affected:< 260304

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

CVSS:3.1/AV:A/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 and hardware version
    Log into the router web management interface and locate the System Tools > Firmware Upgrade or Status page to confirm the exact model number (TL-WR802N, TL-WR841N, or TL-WR840N) and hardware version (v4, v14, or v6 respectively).
    Affected if The device is a TP-Link TL-WR802N v4, TL-WR841N v14, or TL-WR840N v6.
  2. Check installed firmware version
    In the router web interface, navigate to the firmware version information (usually under Status or System Tools > Firmware Upgrade) and note the firmware build number.
    Affected if The firmware version is below 260304 for TL-WR802N or TL-WR840N, or below 260303 for TL-WR841N.
  3. Verify administrative access is enabled
    Confirm that the router web management interface is accessible and that administrator credentials are configured. Check if remote management is enabled under Advanced > System Tools > Remote Management.
    Affected if The router administrative interface is accessible over the network, especially if remote management is enabled.
  4. Confirm configuration import feature exists
    Navigate to the router settings menu (typically under System Tools > Backup & Restore or Configuration) to verify if a configuration file import or restore function is present.
    Affected if The configuration import/restore functionality is accessible to authenticated users.
  5. Check for unauthorized configuration files
    Review any recently uploaded or modified configuration files on the device. Look for unexpected entries in saved configuration backups, particularly related to port trigger settings.
    Affected if Configuration files contain unexpected commands, scripts, or port trigger entries not configured by the administrator.

The device is affected if it is a TP-Link TL-WR802N v4, TL-WR841N v14, or TL-WR840N v6 running firmware version below 260304 (or 260303 for TL-WR841N) and the administrative interface with configuration import capability 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.

From vendor data
Upgrade available Upgrade to 260303 / 260304 or later
Fixed in 260303260304
Interim mitigation

Apply vendor firmware updates when available, restrict administrative access to trusted users only, and consider network segmentation to limit exposure to the configuration import function.

Fix this in Tl Wr802n Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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