Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacent network access to captive portal segment
  2. Delivery
    Identify captive portal service endpoint
  3. Exploit
    Send unauthenticated session termination request
  4. Execution
    All active portal sessions cleared
  5. Persist
    Affected users forced to re-authenticate
  6. Impact
    Repeated requests maintain denial-of-service condition

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The captive portal feature must be enabled on the affected device - this is a deployable feature, not always active by default, so devices not using captive portal are not exposed. The attacker must have adjacent network access (AV:A per CVSS 4.0), meaning they must be on the same broadcast domain, VLAN, or directly connected network segment as the captive portal service interface - remote internet-based attackers cannot reach it without this adjacency. AT:P in the CVSS 4.0 vector confirms this specific network positioning requirement. No authentication is required once adjacency is established (PR:N). No user interaction is needed. Exploitation is limited to availability impact only - confidentiality and integrity of data are not affected. The vulnerability does not grant access to network resources, credentials, or device configuration; it only disrupts active portal sessions.

Impact

The CVSS 4.0 base score of 6.0 with vector AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N accurately reflects the threat profile. The adjacent-network attack vector (AV:A) is the dominant risk-limiting factor: exploitation requires the attacker to be on the same broadcast domain, VLAN, or directly connected network segment as the captive portal service - a credential-less internet attacker cannot trigger this remotely. The AT:P modifier further refines this by acknowledging the specific network position prerequisite. Impact is purely availability (VA:H with no confidentiality or integrity breach), meaning confidential data is not exposed and network configurations cannot be altered. No KEV listing and no public exploit code have been identified at time of analysis, keeping real-world exploitation risk moderate rather than critical despite the trivial technical complexity once the adjacency requirement is met. The primary concern is guest-network or enterprise-edge disruption: a malicious user already on the guest VLAN could repeatedly clear captive portal sessions to deny service to all other users on that segment. EPSS data was not provided in the input and cannot be inferred.

Exploit ScenarioDerived

An attacker who gains access to the guest Wi-Fi or adjacent network segment served by a captive portal on a vulnerable Omada router sends unauthenticated HTTP requests targeting the captive portal session management endpoint, forcing termination of all active user sessions. All connected users are immediately logged out of the captive portal and must re-authenticate to regain internet access. No public exploit code has been identified, but the attack requires only basic HTTP request crafting against the local portal endpoint - no credentials or special tooling needed.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 20, 2026

Captive portal session management across multiple TP-Link Omada ER and DR series routers exposes unauthenticated session-termination functions to any attacker with adjacent network access, allowing forced logout of specific users or full session clearance without credentials. Nineteen hardware models running firmware prior to late June-July 2026 builds are confirmed affected per EUVD data. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the low attack complexity combined with zero authentication requirements makes adjacent-network exploitation straightforward once an attacker is positioned on the same network segment as the captive portal service.

RemediationAI

The primary fix is to upgrade firmware on all affected Omada ER and DR series devices to the patched builds listed in the EUVD data, all dated between June 25 and July 23, 2026. Firmware can be obtained from https://www.omadanetworks.com/us/support/download/ or https://www.omadanetworks.com/en/support/download/, with full model-specific guidance in the vendor advisory at https://www.tp-link.com/us/support/faq/5256/. Patch availability is confirmed by the vendor (TP-Link/Omada Networks). As a compensating control prior to patching, administrators should place the captive portal service interface on a dedicated VLAN or network segment that restricts which client devices can reach the portal management endpoints - limiting adjacency reduces exposure since AV:A means only co-located hosts can exploit this. Disabling the captive portal feature entirely on devices where it is not operationally required eliminates the attack surface with no side effects for deployments that do not use it. Note that VLAN isolation does not fully eliminate risk if legitimate captive portal clients are untrusted (e.g., public guest users), as they inherently share the adjacent segment.

Affected VersionsENISA

ER603WP-4G-Outdoor v1 0 <1.0.2 Build 20260723 Rel.43271
ER703WP-4G-Outdoor v1 0 <1.1.7 Build 20260723 Rel.41712
ER701-5G-Outdoor v1 0 <1.0.3 Build 20260723 Rel.40931
DR3650v-4G v1 0 <1.2.0 Build 20260630 Rel.83347
ER8411 v1 0 <1.4.1 Build 20260708 Rel.64832
ER7406 v1 0 <1.3.4 Build 20260625 Rel.43136
DR3150 v1 0 <1.0.1 Build 20260722 Rel.16854
ER706WP-4G v1 0 <1.1.11 Build 20260723 Rel.41624
ER706W-4G v2 0 <2.1.11 Build 20260723 Rel.41624
ER7412-M2 v1 0 <1.2.0 Build 20260630 Rel.82947
ER605W v2 0 <2.0.4 Build 20260723 Rel.43763
ER7212PC v2 0 <2.4.3 Build 20260722 Rel.40250
ER7206 v2 0 <2.3.5 Build 20260625 Rel.43136
DR3650v v1 0 <1.2.0 Build 20260630 Rel.83311
ER707-M2 v1 0 <1.4.4 Build 20260625 Rel.43063
ER706W v1 0 <1.2.11 Build 20260723 Rel.41567
ER605 v2 0 <2.4.4 Build 20260630 Rel.14398
ER706W-4G v1 0 <1.2.6 Build 20260723 Rel.41321
DR3220v-4G v1 0 <1.2.0 Build 20260630 Rel.82652

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-306 (Missing Authentication for Critical Function) describes the root cause: the captive portal service on affected TP-Link Omada devices exposes session management endpoints - including individual session termination and full session clearance - without requiring any authentication token, credential, or session context from the caller. Captive portals are network access control mechanisms typically deployed in guest Wi-Fi, hotel, or enterprise edge networks to gate internet access pending user login. The affected CPE strings identify TP-Link Systems Inc. Omada-branded VPN routers and gateways spanning ER605, ER606, ER706, ER707, ER7206, ER7212PC, ER7406, ER7412-M2, ER8411, DR3150, DR3220v, and DR3650v hardware lines, all version 1 or 2 hardware revisions. The CVSS 4.0 vector includes AT:P (Attack Requirements: Present), indicating the attacker must be positioned on the adjacent network segment where the captive portal service is reachable - this is a structural prerequisite that limits exposure compared to internet-facing vulnerabilities.

Know when Er7212Pc V2 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 6.0 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Adjacent-network access with no authentication required; impact is solely high availability via uncontrolled session termination; no confidentiality or integrity breach occurs.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

An unauthenticated attacker with network access to the captive portal service of an affected device can terminate active captive portal sessions, including forcing logout of specific users or clearing all active sessions. Affected users must re-authenticate to regain access.

Successful exploitation may allow termination of individual or all active captive portal sessions, causing temporary service disruption and requiring users to re-authenticate.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
popular SMB and branch-office networking line, not ubiquitous enterprise
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy