CVE-2025-40943: Affected devices do not properly sanitize contents of trace files.
Affected devices do not properly sanitize contents of trace files.
This could allow an attacker to inject code through social engineering an authorized user, who has the function right "Read diagnostics", to import a specially crafted trace file.
The malicious trace file is insufficiently sanitized and malicious code could be executed in the clients browser session and trigger PLC operations via the webserver that the legitimate user is authorized to perform.
Security readout for executives and security teams
Plain-English summary
A malicious trace file could make a legitimate Siemens PLC web user perform actions they are allowed to perform. The attack depends on social engineering a user with the "Read diagnostics" right into importing the file. Because PLC operations may be triggered through the webserver, the business risk is high for exposed operational environments.
Executive priority
Prioritize this for OT environments because the CVSS score is critical and the described outcome can affect PLC operations. Immediate focus should be exposure reduction, role review, and vendor-guidance tracking rather than assuming exploitation is already occurring.
Technical view
CVE-2025-40943 is an insufficient sanitization issue in trace-file handling on listed Siemens SIMATIC controller products. Imported crafted trace content can execute malicious code in the authorized client browser session and use that session to trigger PLC operations via the device webserver. The record lists CWE-95 and CVSS 3.1 score 9.6.
Likely exposure
Exposure is most likely where affected Siemens SIMATIC Drive Controller, ET 200SP, Open Controller, or S7-1500 models use webserver diagnostics workflows and users can import trace files. Exact affected version ranges are unclear in the bundle because versions are listed only as "0" with unknown default status.
Exploitation context
The bundle does not show known active exploitation, and KEV is false. Exploitation requires user interaction: an attacker must persuade an authorized user with "Read diagnostics" rights to import a crafted trace file. Impact may include confidentiality, integrity, and availability consequences through authorized PLC operations.
Researcher notes
Evidence supports a browser-session code injection path through crafted trace-file import, but the bundle lacks fixed-version details, proof-of-concept status, and specific Siemens remediation text. Do not generalize beyond the listed SIMATIC products without consulting SSA-452276 and the CVE record.
Mitigation direction
Review Siemens SSA-452276 for official updates, version guidance, and mitigations.
Limit "Read diagnostics" rights to users who operationally require them.
Restrict access to PLC webservers from untrusted networks.
Treat externally supplied trace files as untrusted and avoid importing them.
Educate authorized users about malicious diagnostic trace-file handling.
Validation and detection
Inventory listed Siemens SIMATIC controller models in operational environments.
Identify users and roles with the "Read diagnostics" function right.
Confirm whether PLC webservers are reachable from non-administrative networks.
Review procedures for importing diagnostic trace files.
Check Siemens advisory status for each deployed model and firmware version.
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 · medium confidence lookup
CWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
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.
2CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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-95 · source CWE mapping
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.