CVE-2025-13036: Rockwell Automation FactoryTalk Historian Site Edition - Authentication Bypass
An authentication
bypass security issue exists within FactoryTalk Historian Site Edition. By
continually sending requests to the login endpoint, an attacker may obtain a
valid authentication token.
Security readout for executives and security teams
Plain-English summary
FactoryTalk Historian SE v11 has a critical login weakness. Repeated requests to the login endpoint may let an unauthenticated attacker obtain a valid authentication token, bypassing normal access controls. For OT environments, this could affect confidentiality and integrity of historian data and supporting operations.
Executive priority
Treat this as urgent for any environment running FactoryTalk Historian SE v11. The issue can bypass authentication and affects an OT data platform, but current sources do not confirm active exploitation. Prioritize inventory, exposure reduction, vendor guidance, and monitoring.
Technical view
The issue is an authentication bypass in Rockwell Automation FactoryTalk Historian Site Edition v11, mapped to CWE-362. The CVSS v4.0 score is 9.2 with network access, low complexity, no privileges, and no user interaction. The published description indicates repeated login endpoint requests can result in a valid token.
Likely exposure
Organizations running Rockwell Automation FactoryTalk Historian SE v11 are the affected population identified in the bundle. Exposure is higher where the login endpoint is reachable from broad internal networks, remote access paths, vendor access, or internet-adjacent segments. Other versions are not identified as affected in the provided sources.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The described condition is remotely reachable and unauthenticated, but the CVSS vector includes attack requirements, meaning exploitation depends on specific request timing or conditions. No exploit availability is cited in the bundle.
Researcher notes
Evidence is limited to the CVE record, CVE List entry, and Rockwell advisory reference. Do not assume affected versions beyond v11 or claim exploitation in the wild. Focus validation on version confirmation, authentication exposure, log indicators, and whether Rockwell guidance has been applied.
Mitigation direction
Review Rockwell advisory SD1773 for the vendor-prescribed remediation.
Identify all FactoryTalk Historian SE v11 deployments.
Prioritize remediation for systems reachable from untrusted or broad networks.
Restrict access to authentication interfaces where operationally feasible.
Monitor for repeated login endpoint requests and unexpected token activity.
Track vendor updates until remediation is verified complete.
Validation and detection
Confirm product name and version on each historian server.
Compare deployment status against Rockwell advisory SD1773.
Review network paths that can reach the login endpoint.
Check authentication logs for unusual repeated login requests.
Verify applied fixes or compensating controls with change records.
Document remaining exposed instances and remediation owners.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.