CVE-2025-7353
Published: 14 August 2025
Summary
CVE-2025-7353 is a critical-severity Initialization of a Resource with an Insecure Default (CWE-1188) vulnerability in Rockwellautomation (inferred from references). Its CVSS base score is 9.3 (Critical).
Operationally, ranked in the top 15.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2025-7353 is a critical vulnerability in the web-based debugger agent that is enabled by default on Rockwell Automation ControlLogix Ethernet Modules. The flaw, tracked under CWE-1188, permits an attacker who connects using a specific IP address to interact directly with the agent and perform unauthorized operations on device memory and execution state.
Remote unauthenticated attackers can exploit the issue over the network to dump memory contents, alter memory values, and redirect execution flow. The CVSS 4.0 score of 9.3 reflects the absence of required authentication or user interaction combined with high impact on confidentiality, integrity, and availability of the targeted modules.
The vendor has published an advisory at https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1732.html that addresses the issue. The associated EPSS score has remained flat at 0.0216 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-24813
Vulnerability details
A security issue exists due to the web-based debugger agent enabled on Rockwell Automation ControlLogix® Ethernet Modules. If a specific IP address is used to connect to the WDB agent, it can allow remote attackers to perform memory dumps, modify…
more
memory, and control execution flow.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires documented secure initialization practices and avoidance of insecure defaults in configuration baselines.
Reviewing and updating baseline when components are installed or upgraded prevents initialization with insecure defaults.
Requiring explicit configuration to minimal functionality overrides insecure defaults that would otherwise enable excess capabilities.
Tailoring replaces or augments insecure default initializations with system-specific values and compensating controls before deployment.
Central configuration overrides or replaces insecure default initializations that would otherwise be left unchanged on each system.
SCRM practices during acquisition and configuration management address insecure default initializations shipped by vendors.
Scans detect resources initialized with insecure defaults that create exploitable conditions.
Instruction on secure initialization of security controls prevents leaving resources with insecure defaults after installation.