dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-11696

HIGH · 8.9 CVSS v4.0 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 local server-side request forgery (SSRF) security issue exists within Studio 5000® Simulation Interface™ via the API. This vulnerability allows any Windows user on the system to trigger outbound SMB requests, enabling the capture of NTLM hashes.

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 local SSRF vulnerability in Studio 5000 Simulation Interface API allows any authenticated Windows user to trigger outbound SMB requests, enabling NTLM hash capture via SMB relay attacks. This stems from insufficient validation of outbound network requests within the application's context.

MitigationRestrict outbound SMB connections from the application and enforce SMB signing to prevent NTLM relay attacks. Consider disabling NTLM authentication in favor of Kerberos where possible, and network-segment the application server to block unnecessary SMB outbound traffic.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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 checks

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

  1. Verify Studio 5000 Simulation Interface installation
    Check if Studio 5000 (specifically the Simulation Interface component) is installed on the system. Look in Program Files for Rockwell Software folders or check Windows Registry under HKLM\SOFTWARE\Rockwell Software for Studio 5000 components.
    Affected if Studio 5000 Simulation Interface is installed and the API service is present on the system.
  2. Identify the installed version
    Locate the Simulation Interface executable or DLL version. Check the file properties of rslogix5000.exe, SimulationInterface.exe, or related DLLs in the installation directory, or query the Windows Registry for the version value under the product's registry key.
    Affected if The installed version matches the affected version range for CVE-2025-11696.
  3. Confirm the Simulation Interface API is enabled
    Check if the Simulation Interface service is running and the API endpoint is accessible. Look for configuration files (e.g., siminterface.config, api.config) or service settings that enable the API functionality.
    Affected if The Simulation Interface API service is running and configured to accept requests.
  4. Check if Windows authentication (NTLM) is in use
    Review the application's authentication configuration or check the Windows event logs for NTLM usage patterns. Examine the service account configuration for the Simulation Interface service.
    Affected if The application uses NTLM authentication for user verification.
  5. Verify SMB relay exposure
    Inspect network configuration or firewall rules to determine if outbound SMB connections (port 445) are permitted from the application server to arbitrary destinations.
    Affected if The system can initiate outbound SMB connections without restriction, allowing potential NTLM hash capture.

A user is affected if Studio 5000 Simulation Interface with the vulnerable API component is installed, the API is enabled, and the environment allows outbound SMB connections with NTLM authentication in use.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict outbound SMB connections from the application and enforce SMB signing to prevent NTLM relay attacks. Consider disabling NTLM authentication in favor of Kerberos where possible, and network-segment the application server to block unnecessary SMB outbound traffic.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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