basicsecurity.net
Proof, not just disclosure.
Threats / TP-Link / CVE-2023-33538
CVE-2023-33538 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

TP-Link Multiple Routers vulnerability

TP-Link routers contain a command injection vulnerability in the WlanNetworkRpm component, allowing remote code execution. Affected end-of-life models include TL-WR940N, TL-WR841N, and TL-WR740N variants.

Verdict

Today item — known-exploited.

This command injection vulnerability enables unauthenticated remote attackers to execute arbitrary commands on vulnerable TP-Link routers. The high EPSS score and active exploitation indicate immediate risk to unpatched devices, particularly concerning given the end-of-life status of affected models

CISA KEV Yes · 2025-06-163EPSS 0.42568 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-16).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.42568 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: TP-Link, Multiple Routers. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious request targeting the /userRpm/WlanNetworkRpm endpoint with injected shell commands.
Business
Network infrastructure is compromised, enabling lateral movement into corporate systems and data exfiltration.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute commands to establish persistent access and modify router configurations for traffic interception.
Business
Sensitive communications are monitored; customer data and intellectual property are exposed to theft.
3

Lateral reach — past segmentation narrative 3

Attacker
I pivot from the compromised router to connected devices and internal network segments.
Business
Operational continuity is disrupted; remediation costs and incident response burden escalate significantly.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.