Skip to main content
VulnerabilityPublished

CVE-2025-41672: Wago Device Sphere · Insecure Default

Affects Wago Device SphereSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% 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:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WAGO Wago Device SphereAffected
  • =1.0.0
Fixed in–

AI-suggested

Immediate mitigation steps should include: 1) Isolating the Wago Device Sphere instances from public networks until a patch is available, restricting access to trusted internal networks only. 2) Conducting an inventory of all connected devices and monitoring for unusual authentication tokens or access patterns indicative of JWT forgery. 3) Implementing network-level controls such as firewalls and intrusion detection/prevention systems (IDS/IPS) to detect and block unauthorized access attempts. 4) Engaging with WAGO support to obtain any available workarounds or interim fixes, such as replacing default certificates with unique, securely generated ones. 5) Applying strict access control policies and multi-factor authentication on management consoles where possible to reduce risk. 6) Preparing incident response plans specifically for ICS compromise scenarios, including backup and recovery procedures. 7) Monitoring threat intelligence feeds for emerging exploits targeting this vulnerability. Organizations should prioritize patching as soon as WAGO releases an official update and validate the integrity of their device management environments regularly.

Description

A remote unauthenticated attacker may use default certificates to generate JWT Tokens and gain full access to the tool and all connected devices.

References

Community reviews

Loading reviews…