dbcve.org
1756 En2tr Series A FirmwareOperating system · Rockwellautomation

CVE-2025-8007

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 7.001 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
A security issue exists in the protected mode of 1756-EN4TR and 1756-EN2TR communication modules, where a Concurrent Forward Close operation can trigger a Major Non-Recoverable (MNFR) fault. This condition may lead to unexpected system crashes and loss of device availability.

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 confidence

A security vulnerability exists in the protected mode of Rockwell Automation 1756-EN4TR and 1756-EN2TR EtherNet/IP communication modules where a Concurrent Forward Close operation can trigger a Major Non-Recoverable (MNFR) fault, causing unexpected system crashes and loss of device availability.

MitigationApply firmware updates from Rockwell Automation when available; implement network segmentation to reduce attack surface and monitor for MNFR fault conditions; coordinate firmware updates during planned maintenance windows given the critical nature of these communication modules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
1756 En2tr Series A FirmwareOperating system
Affected:< 7.001
1756 En2tr Series B FirmwareOperating system
Affected:< 7.001
1756 En2tr Series C FirmwareOperating system
Affected:< 7.001
1756 En4tr FirmwareOperating system
Affected:< 7.001
1756 En4trxt FirmwareOperating system
Affected:< 7.001

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed EtherNet/IP module model
    Access the controller's hardware inventory through Rockwell Automation's Studio 5000 Logix Designer or RSLinx Classic. Locate the communication module in the I/O configuration tree and note the exact model number (1756-EN2TR, 1756-EN4TR, or 1756-EN4TRXT).
    Affected if The model is 1756-EN2TR (any series) or 1756-EN4TR/1756-EN4TRXT.
  2. Determine the installed firmware version
    In RSLinx Classic, right-click the module and select 'Device Properties' to view the firmware revision. Alternatively, use the 'Firmware Revision' field in the module's properties within Studio 5000 Logix Designer. Record the firmware version number.
    Affected if Firmware version is lower than 7.001.
  3. Check if protected mode is enabled
    In Studio 5000 Logix Designer, open the module's properties for the EtherNet/IP communication module. Look for the 'Protected Mode' or 'Security' settings configuration. Verify whether protected mode is currently enabled or disabled.
    Affected if Protected mode is enabled on the module.
  4. Review for existing MNFR fault conditions
    In Studio 5000 Logix Designer, access the controller's 'Controller Properties' and view the 'Major Faults' tab or check the module's fault information in RSLinx Classic. Look for Major Non-Recoverable (MNFR) faults related to the EtherNet/IP module.
    Affected if An MNFR fault is present and tied to the communication module.

You are affected if your installed module is a 1756-EN2TR or 1756-EN4TR/1756-EN4TRXT with firmware version below 7.001 and protected mode is enabled, or if you observe MNFR faults on the module.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 7.001 or later
Fixed in 7.001
Interim mitigation

Apply firmware updates from Rockwell Automation when available; implement network segmentation to reduce attack surface and monitor for MNFR fault conditions; coordinate firmware updates during planned maintenance windows given the critical nature of these communication modules.

Recommended fix High confidence

Firmware version 7.001 for 1756-EN2TR (Series A/B/C) and 1756-EN4TR/EN4TRXT

  1. Identify the specific module series (EN2TR Series A/B/C, EN4TR, or EN4TRXT) in your system
  2. Check the current firmware version of the affected module via the control system programming software or web interface
  3. Navigate to the Rockwell Automation Product Compatibility and Download Center (PCDC) to obtain firmware version 7.001 or later for your specific module
  4. Review all prerequisites and firmware update procedures in the official Rockwell Automation firmware release notes
  5. Connect to the module and upload the new firmware using the appropriate Rockwell update tool (such as FactoryTalk AssetCentre or RSLinx Classic)
  6. After firmware update completes, verify the new version is 7.001 or later
  7. Confirm the module returns to operational state and test normal communication functions
Caveat Review release notes for any changes to functionality or compatibility with controllers; firmware updates in industrial environments should be tested in a non-production setting first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 1756 En2tr Series A Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8007 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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