VulnerabilityPublished 16 Jul 2025

CVE-2025-6983: TP-Link System Archer C1200 · Clickjacking

Affects TP-Link System Archer C1200Source CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Active
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
TP-Link System Inc. Archer C1200	Affected =0	Fixed in–

AI-suggested

Network administrators and users should immediately restrict access to the router's web management interface by disabling remote management and limiting local network access to trusted devices only.
Employ browser security features such as X-Frame-Options or Content Security Policy (CSP) headers to prevent framing of the router's management interface, if configurable.
Educate users to avoid clicking on suspicious links or visiting untrusted websites, as user interaction is required for exploitation.
Monitor network traffic for unusual DNS queries or configuration changes that could indicate exploitation attempts.
Regularly check TP-Link's official channels for firmware updates or patches addressing this vulnerability and apply them promptly once available.
Consider replacing affected devices with models that have updated firmware or better security controls if patching is not feasible.
Use network segmentation to isolate critical systems from devices like routers that may be vulnerable to UI-based attacks.
Implement multi-factor authentication on router management interfaces if supported to reduce risk from UI manipulation.

Description

A Clickjacking vulnerability in TP-Link Archer C1200 web management page allows an attacker to trick users into performing unintended actions via rendered UI layers or frames.This issue affects Archer C1200 <= 1.1.5.

Impact

For European organizations, especially small and medium enterprises (SMEs) and home offices relying on TP-Link Archer C1200 routers, this vulnerability poses a risk of unauthorized configuration changes leading to network compromise. Attackers could redirect traffic through malicious DNS servers, disable security features, or open ports to external threats, undermining network integrity and availability. While large enterprises may use more robust equipment, the widespread use of TP-Link devices in residential and small business environments in Europe means that attackers could leverage this vulnerability as a foothold for broader attacks or espionage. The requirement for user interaction (visiting a malicious webpage) means phishing campaigns or malicious advertisements could be vectors for exploitation. The vulnerability could also be leveraged in targeted attacks against specific users or organizations by tricking them into visiting crafted sites. The lack of authentication requirement increases the risk, as any user on the local network or visiting a malicious site can be targeted. However, the impact on confidentiality is limited as the attacker cannot directly extract sensitive data without further exploitation.

CWE-1021Improper Restriction of Rendered UI Layers or Frames (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
Implementation
The use of X-Frame-Options allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content.
Implementation
A developer can use a "frame-breaker" script in each page that should not be framed. This is very helpful for legacy browsers that do not support X-Frame-Options security feature previously mentioned.
Implementation
This defense-in-depth technique can be used to prevent the improper usage of frames in web applications. It prioritizes the valid sources of data to be loaded into the application through the usage of declarative policies.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.3 (opens in a new tab)
V14.4.7 (opens in a new tab)
Attack patterns
Clickjacking (opens in a new tab)
Flash File Overlay (opens in a new tab)
iFrame Overlay (opens in a new tab)
Task Impersonation (opens in a new tab)
Tapjacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

tp-link.com/us/support/faq/4539/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jul 2025, 20:31 UTC

WeaknessesCWE-1021

Technical details

References

Community reviews

Related threats