VulnerabilityPublished 8 Jan 2026

CVE-2025-68718: Information Exposure

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.4Medium

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

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2026
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 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

AI-suggested

1. Immediately identify and inventory all KAYSUS KS-WR1200 routers running firmware version 107 within the network. 2. Segment networks to isolate these routers from general user LAN segments, restricting access to trusted management stations only. 3. Implement strict network access controls (e.g., 802.1X, NAC) to prevent unauthorized devices from connecting to LAN segments where these routers reside. 4. Monitor network traffic for unauthorized SSH or TELNET connections to these routers and set up alerts for suspicious login attempts. 5. Disable TELNET and SSH services at the network level using firewall rules if device-level disabling is impossible. 6. Engage with the vendor for firmware updates or patches; if none are available, consider replacing affected devices with models that do not have hardcoded credentials. 7. Educate internal staff about the risks of connecting unauthorized devices to the LAN and enforce strict physical and logical access controls. 8. Use network intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts. 9. Regularly audit router configurations and logs for signs of compromise. 10. Prepare incident response plans specific to router compromise scenarios.

Description

KAYSUS KS-WR1200 routers running firmware version 107 have a vulnerability where SSH and TELNET services are exposed on the LAN interface with hardcoded root credentials (root:12345678). These credentials cannot be changed or disabled by the administrator, and changing the GUI password does not affect SSH/TELNET access. This allows any attacker with LAN access to gain root-level control of the device without authentication barriers. The vulnerability has a CVSS score of 5.4, indicating medium severity, with low impact on confidentiality and integrity but no impact on availability. No known exploits are currently reported in the wild. This issue poses a significant risk in environments where these routers are deployed, especially in internal networks without strict segmentation. European organizations using these routers should prioritize detection and network segmentation to mitigate risk.

Impact

For European organizations, this vulnerability presents a moderate risk primarily in internal network environments where KAYSUS KS-WR1200 routers are deployed. An attacker with LAN access—such as a malicious insider, compromised device, or visitor connected to the internal network—can gain root access to the router, potentially allowing interception or manipulation of network traffic, unauthorized configuration changes, and lateral movement within the network. This could lead to data confidentiality breaches and integrity violations, especially in sensitive sectors like finance, healthcare, or critical infrastructure. Although the vulnerability does not directly impact availability, the loss of control over network routing and security policies could indirectly cause service disruptions. The inability to change or disable the hardcoded credentials means that traditional password management policies are ineffective, increasing the risk of persistent compromise. Organizations with poor network segmentation or guest network controls are particularly vulnerable. The medium CVSS score reflects the limited attack vector (LAN adjacent) but significant privilege escalation potential.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 15 Jan 2026, 22:05 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats