CVE-2025-7350
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security issue affecting multiple Cisco devices also directly impacts Stratix® 5410, 5700, and 8000 devices. This can lead to remote code execution by uploading and running malicious configurations without authentication.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA pre-authentication remote code execution vulnerability in Rockwell Automation Stratix 5410, 5700, and 8000 industrial Ethernet switches, stemming from inherited Cisco technology, allows unauthenticated attackers to upload and execute malicious configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Stratix switch modelAccess the switch CLI or web interface and run 'show version' or check the device info page to confirm the exact model number (5410, 5700, or 8000)Affected if Model is Stratix 5410, 5700, or 8000 - these are the affected product lines
-
Determine firmware versionRun 'show version' in the switch CLI or check the firmware version in the web interface. Compare the displayed firmware version against any Rockwell Automation advisories for this CVE.Affected if Firmware version is unpatched per the vendor's CVE-2025-7350 advisory (version comparison required against vendor-published affected versions)
-
Check management interface exposureVerify if the switch management interface (HTTP/HTTPS, SSH, Telnet) is accessible from untrusted networks by reviewing firewall rules, VLAN configuration, or using 'show ip interface' to list accessible IPsAffected if Management interface is reachable from outside the trusted management network (pre-authentication flaw means any network access is risky)
-
Audit configuration upload logsReview switch logs for any unexpected configuration upload events. Use 'show logging' or check syslog exports for entries containing 'configure replace', 'copy running-config', or configuration restore activities.Affected if Unexpected configuration uploads or restores appear in logs, especially from unfamiliar sources
-
Inspect for unauthorized configuration changesCompare the current running configuration against known-good baselines using 'show running-config' versus previously saved configuration files, checking for unfamiliar commands or injected code.Affected if Running configuration contains unexpected commands, scripts, or modifications not authored by legitimate administrators
A defender is affected if they operate an unpatched Stratix 5410, 5700, or 8000 switch with management interfaces accessible to untrusted networks, regardless of whether exploitation has occurred.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided patches or firmware updates when released; until then, restrict network access to management interfaces and monitor for unauthorized configuration upload attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7350 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data