CVE-2025-6541: OS command injection using information obtained from the web management interface

17

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.7% (30-day exploitation probability)+8
Technical severity (high)+6
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.69%

ahead of 52% of scored CVEs · Oct 14, 2026

Affects

TP-Link Systems Inc.

Er605 Firmware and 15 more

CVSS base

8.8

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (TP-Link Systems Inc. Er605 Firmware, TP-Link Systems Inc. Er706w Firmware, TP-Link Systems Inc. Er706w-4g Firmware…).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
TP-Link Systems Inc.	Er605 Firmware	version 2.3.1< 2.3.1	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er706w Firmware	< 1.2.1version 1.2.1	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er706w-4g Firmware	version 1.2.1< 1.2.1	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er707-m2 Firmware	< 1.3.1version 1.3.1	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er7206 Firmware	< 2.2.2version 2.2.2	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er7212pc Firmware	< 2.1.3version 2.1.3	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er7412-m2 Firmware	version 1.1.0< 1.1.0	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Er8411 Firmware	< 1.3.3version 1.3.3	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Festa gateways	< FR365 1.1.10, FR205 1.0.3, FR307 1.2.5	Vulnerable	CVE Program (cve.org) e CISA ADP
TP-Link Systems Inc.	Fr205 Firmware	< 1.0.3version 1.0.3	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Fr307-m2 Firmware	< 1.2.5version 1.2.5	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Fr365 Firmware	< 1.1.10version 1.1.10	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	G36 Firmware	< 1.1.4version 1.1.4	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	G611 Firmware	< 1.2.2version 1.2.2	Vulnerable	NIST National Vulnerability Database
TP-Link Systems Inc.	Omada gateways	< ER8411 1.3.3, ER7412-M2 1.1.0, ER707-M2 1.3.1, ER7206 2.2.2, ER605 2.3.1, ER706W	Vulnerable	CVE Program (cve.org) e CISA ADP
TP-Link Systems Inc.	Omada Pro gateways	< G36 1.1.4, G611 1.2.2	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.6	CVSS 4.0	High	—	—	f23511db-6c3e-4e32-a477-6aa17d310630 via NIST National Vulnerability Database
8.6	CVSS 4.0	High	—	—	TPLink via CVE Program (cve.org) e CISA ADP
8.8	CVSS 3.1	High	2.8	5.9	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.69%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · tp-link systems inc./omada gateways, tp-link systems inc./festa gateways, tp-link systems inc./omada pro gateways
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 8.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Oct 20, 2025 · TPLink

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

support.omadanetworks.com/en/document/108455/
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database
www.tp-link.com/us/business-networking/soho-festa-gateway/
Product, product, NIST National Vulnerability Database
www.omadanetworks.com/us/business-networking/all-omada-router/
Product, product, NIST National Vulnerability Database
www.omadanetworks.com/us/business-networking/omada-pro-router-wired-router/
Product, product, NIST National Vulnerability Database

Elsewhere on this site

TP-Link Systems Inc.
every CVE for this vendor

Injection
same class

CWE-78
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2025-9290 Authentication Weakness on Omada Controllers, Gateways and Access Points Jan 22, 2026
Critical CVE-2025-6542 OS command injection in multiple parameters Oct 20, 2025
High CVE-2025-7850 Authenticated OS command execution Oct 20, 2025
Critical CVE-2025-7851 Unauthorized root access via debug functionality Oct 20, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-6541 is "OS command injection using information obtained from the web management interface", rated High. It affects Er605 Firmware (TP-Link Systems Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.69% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.