dbcve.org
Er8411 FirmwareOperating system · Tp Link

CVE-2025-7850

HIGH · 7.2 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to 1.1.0 / 1.2.1 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
A command injection vulnerability may be exploited after the admin's authentication on the web portal on Omada gateways.

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 web portal interface of TP-Link Omada gateways. An authenticated administrator can potentially inject and execute arbitrary operating system commands through the vulnerable web interface, leading to full compromise of the gateway device.

MitigationRestrict administrative access to the Omada gateway web portal to trusted IP addresses or networks, implement strong admin credentials, and apply vendor-supplied firmware updates once available. Network segmentation can limit exposure if the gateway is compromised.

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
Er8411 FirmwareOperating system
Affected:< 1.3.3= 1.3.3
Er7412 M2 FirmwareOperating system
Affected:< 1.1.0= 1.1.0
Er707 M2 FirmwareOperating system
Affected:< 1.3.1= 1.3.1
Er7206 FirmwareOperating system
Affected:< 2.2.2= 2.2.2
Er605 FirmwareOperating system
Affected:< 2.3.1= 2.3.1
Er706w FirmwareOperating system
Affected:< 1.2.1= 1.2.1
Er706w 4g FirmwareOperating system
Affected:< 1.2.1= 1.2.1
Er7212pc FirmwareOperating system
Affected:< 2.1.3= 2.1.3

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 the TP-Link Omada gateway model
    Log into the Omada web portal and navigate to System > System Info or check the device label/quick start guide. Look for the model name such as ER8411, ER7412 M2, ER707 M2, ER7206, ER605, ER706w, or ER7212PC.
    Affected if The device model matches one of the affected models listed in the CVE (ER8411, ER7412 M2, ER707 M2, ER7206, ER605, ER706w, ER706w 4G, ER7212PC).
  2. Locate the firmware version in the web interface
    In the Omada web portal, go to System > System Info or Settings > Firmware Upgrade. The current firmware version is displayed on this page.
    Affected if The displayed firmware version is equal to or lower than the vulnerable version for your model: ER8411 (1.3.3), ER7412 M2 (1.1.0), ER707 M2 (1.3.1), ER7206 (2.2.2), ER605 (2.3.1), ER706w (1.2.1), ER7212PC (2.1.3).
  3. Verify the web portal is network accessible
    Confirm that the Omada gateway web management interface (typically ports 80 or 443) is reachable from network segments beyond the trusted administration network.
    Affected if The web portal is accessible from untrusted networks, increasing exposure to unauthenticated or compromised attackers who could attempt credential theft.

You are affected if you have a TP-Link Omada gateway model listed in the CVE and your current firmware version is equal to or lower than the version specified for that model.

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 / 1.2.1 / 1.3.1 or later
Fixed in 1.1.01.2.11.3.1
Interim mitigation

Restrict administrative access to the Omada gateway web portal to trusted IP addresses or networks, implement strong admin credentials, and apply vendor-supplied firmware updates once available. Network segmentation can limit exposure if the gateway is compromised.

Recommended fix High confidence

Er8411: upgrade to firmware > 1.3.3; Er7412 M2: upgrade to firmware > 1.1.0; Er707 M2: upgrade to firmware > 1.3.1; Er7206: upgrade to firmware > 2.2.2; Er605: upgrade to firmware > 2.3.1; Er706w: upgrade to firmware > 1.2.1; Er706w 4g: upgrade to firmware > 1.2.1; Er7212pc: upgrade to firmware > 2.

  1. 1. Identify the exact model number of your Omada gateway from the device label or web UI.
  2. 2. Access the Omada gateway's web management interface using an admin account.
  3. 3. Navigate to System > Firmware Upgrade (or similar path depending on model).
  4. 4. Download the appropriate fixed firmware version for your model from TP-Link's official support site (www.tp-link.com).
  5. 5. Upload the firmware file through the web interface and initiate the upgrade.
  6. 6. Wait for the device to reboot and verify the new firmware version in the web UI.
  7. 7. After upgrade, verify the command injection vulnerability is resolved by confirming normal operation.
Caveat Standard firmware upgrade - backup configuration before upgrading; device will reboot and may require reconfiguration if firmware format changed

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

Fix this in Er8411 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-7850 — 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-7850 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