CVE-2025-41715: WAGO Device Sphere · Missing Authentication
Affects WAGO Device SphereSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WAGO Device Sphere | Affected
| Fixed in– |
AI-suggested
1. Immediate network-level controls: Restrict access to the WAGO Device Sphere management interfaces and databases to trusted internal networks only, using firewalls, VPNs, or network segmentation to prevent unauthorized external access. 2. Implement strong authentication proxies: Deploy reverse proxies or web application firewalls (WAFs) that enforce authentication and authorization before allowing access to the Device Sphere database or management interfaces. 3. Monitor and log access: Enable detailed logging and continuous monitoring of all access attempts to the Device Sphere environment to detect any unauthorized or suspicious activity promptly. 4. Vendor engagement: Engage with WAGO for official patches or updates addressing this vulnerability and apply them as soon as they become available. 5. Incident response readiness: Prepare incident response plans specific to industrial IoT environments to quickly contain and remediate any exploitation attempts. 6. Conduct security assessments: Perform penetration testing and vulnerability scans focused on Device Sphere deployments to identify exposure and verify the effectiveness of mitigations. 7. Configuration review: Review and harden Device Sphere configurations to disable any unnecessary services or interfaces that may expose the database. 8. Data encryption: Where possible, ensure that sensitive data stored in or transmitted by Device Sphere is encrypted to reduce the impact of unauthorized access.
Description
The database for the web application is exposed without authentication, allowing an unauthenticated remote attacker to gain unauthorized access and potentially compromise it.