dbcve.org
Factorytalk LinxApplication · Rockwellautomation

CVE-2025-7972

CRITICAL · 9.1 CVSS v3.1 Published 2025-08-14
Fix available
A fix is available. Upgrade to 6.50 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 within the FactoryTalk Linx Network Browser. By modifying the process.env.NODE_ENV to ‘development’, the attacker can disable FTSP token validation. This bypass allows access to create, update, and delete FTLinx drivers.

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 · high confidence

In FactoryTalk Linx Network Browser, the FTSP token validation is conditionally disabled when the process.env.NODE_ENV environment variable is set to 'development'. An attacker who can control or influence this environment variable can bypass authentication entirely and create, modify, or delete FTLinx drivers, leading to full compromise of the industrial application layer.

MitigationEnsure FTSP token validation is enforced regardless of NODE_ENV setting; remove or fix the conditional logic that bypasses security checks in development mode, and implement environment-agnostic authentication.

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
Factorytalk LinxApplication
Affected:< 6.50

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 FactoryTalk Linx installation
    Check for FactoryTalk Linx installation directories or look in Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Rockwell Software\FactoryTalk Linx
    Affected if FactoryTalk Linx is installed on the system
  2. Check installed version
    Locate the FactoryTalk Linx version information (typically in registry or in the installation folder's version file) and compare it to 6.50
    Affected if The installed version is lower than 6.50 (e.g., 6.40, 6.30, etc.)
  3. Inspect NODE_ENV environment variable
    Check the process.env.NODE_ENV setting for the FactoryTalk Linx Network Browser service or application process - look in system environment variables or the application's runtime configuration
    Affected if NODE_ENV is set to 'development' in the production environment
  4. Verify FTSP token validation status
    Inspect FactoryTalk Linx configuration files or settings that control FTSP token validation - look for settings that may allow token validation to be bypassed based on environment mode
    Affected if FTSP token validation can be disabled or bypassed based on NODE_ENV setting

The environment is affected if FactoryTalk Linx version is below 6.50 AND NODE_ENV is set to 'development', allowing unauthenticated FTLinx driver modifications.

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 6.50 or later
Fixed in 6.50
Interim mitigation

Ensure FTSP token validation is enforced regardless of NODE_ENV setting; remove or fix the conditional logic that bypasses security checks in development mode, and implement environment-agnostic authentication.

Recommended fix High confidence

FactoryTalk Linx 6.50

  1. Back up all FactoryTalk Linx configurations and project data before starting the upgrade process
  2. Download FactoryTalk Linx version 6.50 or later from the official Rockwell Automation website (rockwellautomation.com)
  3. Stop all FactoryTalk Linx services and related applications
  4. Install the FactoryTalk Linx 6.50 upgrade following the Rockwell Automation installation guide
  5. Restart FactoryTalk Linx services after installation completes
  6. Verify that the security fix is active by confirming that modifying process.env.NODE_ENV to 'development' no longer bypasses FTSP token validation
  7. Test that FTLinx driver create, update, and delete operations now require proper authentication
  8. Restore configuration from backup if needed and validate normal operation

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

Fix this in Factorytalk Linx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7972 — 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-7972 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