VulnerabilityPublished 27 Oct 2025

CVE-2025-59460: SICK TLOC100-100 with Firmware <7.1.1 · Use of Weak Credentials

Affects SICK TLOC100-100 with Firmware <7.1.1Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: 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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 27 Oct 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
SICK AG TLOC100-100 with Firmware <7.1.1	Affected =0	Fixed in–

AI-suggested

Immediately upgrade all SICK AG TLOC100-100 devices to firmware version 7.1.1 or later, which addresses the weak credential issue.
Conduct a thorough audit of device configurations to ensure default credentials are replaced with strong, unique passwords following organizational password policies.
Implement network segmentation to isolate industrial control devices from general IT networks and restrict access to trusted management stations only.
Deploy strict access control lists (ACLs) and firewall rules to limit inbound connections to the devices from authorized IP addresses.
Enable logging and monitoring on devices and network segments to detect unauthorized access attempts promptly.
Incorporate multi-factor authentication (MFA) where supported to add an additional layer of security.
Educate operational technology (OT) personnel about the risks of default credentials and the importance of secure configurations.
Establish a vulnerability management process to track firmware updates and security advisories from SICK AG and respond swiftly to new threats.
Consider deploying intrusion detection/prevention systems (IDS/IPS) tailored for industrial protocols to detect anomalous activity targeting these devices.

Description

The system is deployed in its default state, with configuration settings that do not comply with the latest best practices for restricting access. This increases the risk of unauthorised connections.

Impact

For European organizations, especially those in manufacturing, industrial automation, and critical infrastructure sectors, this vulnerability presents a significant risk to operational confidentiality. Unauthorized access could lead to exposure of sensitive process data, intellectual property, or safety system configurations. While the vulnerability does not directly affect system integrity or availability, the confidentiality breach could facilitate further attacks or industrial espionage. Given the critical role of SICK AG devices in European industrial environments, exploitation could undermine trust in automation systems and cause regulatory compliance issues related to data protection. The ease of exploitation without authentication or user interaction increases the likelihood of opportunistic attacks, potentially by cybercriminals or state-sponsored actors targeting European industrial assets. The absence of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score underscores the urgency of addressing the vulnerability to prevent future incidents.

CWE-1391Use of Weak Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker.
Architecture and Design · Operation
When the user changes or sets a password, check the password against a database of already compromised or breached passwords. These passwords are likely to be used in password guessing attacks.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (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

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 11:21 UTC

WeaknessesCWE-1391

Technical details

References

Community reviews

Related threats