Skip to main content
CVE-2025-40817VulnerabilityPublished Updated

CVE-2025-40817: Siemens LOGO! 12/24RCE · Missing Authentication

Affects Siemens LOGO! 12/24RCESource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.84.05 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.84.05
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Upgrade LOGO! 12/24RCE and LOGO! 12/24RCEo and LOGO! 230RCE and LOGO! 230RCEo and LOGO! 24CE and LOGO! 24CEo and LOGO! 24RCE and LOGO! 24RCEo and SIPLUS LOGO! 12/24RCE and SIPLUS LOGO! 12/24RCEo and SIPLUS LOGO! 230RCE and SIPLUS LOGO! 230RCEo and SIPLUS LOGO! 24CE and SIPLUS LOGO! 24CEo and SIPLUS LOGO! 24RCE and SIPLUS LOGO! 24RCEo to 1.84.05.

Affected software

ProductAffectedFixed in
SiemensLOGO! 12/24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 12/24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 230RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 230RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24CEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24CEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensLOGO! 24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 12/24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 12/24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 230RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 230RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24CEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24CEoAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24RCEAffected
  • <1.84.05
Fixed in
  • 1.84.05
SiemensSIPLUS LOGO! 24RCEoAffected
  • <1.84.05
Fixed in
  • 1.84.05

AI-suggested

1. Implement strict network segmentation to isolate Siemens LOGO! devices from general IT networks and restrict access to trusted management stations only. 2. Employ firewall rules and access control lists (ACLs) to limit network traffic to the PLCs, allowing only authorized protocols and sources. 3. Monitor device logs and network traffic for unusual time change commands or anomalies in device behavior. 4. Use secure remote access solutions with multi-factor authentication for any legitimate remote management. 5. Regularly audit and update device firmware and software; apply vendor patches promptly once released. 6. Establish incident response procedures specific to industrial control systems to quickly identify and remediate time manipulation attempts. 7. Consider deploying intrusion detection systems (IDS) tailored for ICS environments to detect unauthorized commands. 8. Train operational technology (OT) personnel on this vulnerability and best practices for securing PLCs. 9. If possible, configure devices to alert on time changes or restrict time-setting commands to authenticated sessions. 10. Collaborate with Siemens support and stay informed on updates or advisories related to this vulnerability.

Description

A vulnerability has been identified in LOGO! 12/24RCE (6ED1052-1MD08-0BA2) (All versions < V1.84.05), LOGO! 12/24RCEo (6ED1052-2MD08-0BA2) (All versions < V1.84.05), LOGO! 230RCE (6ED1052-1FB08-0BA2) (All versions < V1.84.05), LOGO! 230RCEo (6ED1052-2FB08-0BA2) (All versions < V1.84.05), LOGO! 24CE (6ED1052-1CC08-0BA2) (All versions < V1.84.05), LOGO! 24CEo (6ED1052-2CC08-0BA2) (All versions < V1.84.05), LOGO! 24RCE (6ED1052-1HB08-0BA2) (All versions < V1.84.05), LOGO! 24RCEo (6ED1052-2HB08-0BA2) (All versions < V1.84.05), SIPLUS LOGO! 12/24RCE (6AG1052-1MD08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 12/24RCEo (6AG1052-2MD08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 230RCE (6AG1052-1FB08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 230RCEo (6AG1052-2FB08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24CE (6AG1052-1CC08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24CEo (6AG1052-2CC08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24RCE (6AG1052-1HB08-7BA2) (All versions < V1.84.05), SIPLUS LOGO! 24RCEo (6AG1052-2HB08-7BA2) (All versions < V1.84.05). Affected devices do not conduct certain validations when interacting with them. This could allow an unauthenticated remote attacker to change time of the device, which means the device could behave differently.

References

Community reviews

Loading reviews…