CVE-2026-63350: Affected devices do not properly restrict executable content contained in imported trace files.
Noroxi assessment
Priority: Monitor (action score 37/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Affected devices do not properly restrict executable content contained in imported trace files. This could allow an attacker to social engineer an authorized user who holds the function right “Read diagnostics” into importing a specially crafted trace file. Successful exploitation could allow attacker-controlled JavaScript to execute in the user’s browser session and perform PLC operations through the web server within the scope of the user’s authorization.
- Published
- Oct 13, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-95
Report tools
Action score
37
Low priority for now.
- CVSS
- 37 / 40 · 9.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · siemens
- 9.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (siemens). Independent of NVD's CPE analysis and usually ahead of it.
Siemens SIMATIC Drive Controller CPU 1504D TF
- all versionsaffected
Siemens SIMATIC Drive Controller CPU 1507D TF
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1510SP F-1 PN
- all versionsaffected
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1510SP-1 PN
- all versionsaffected
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1512SP F-1 PN
- all versionsaffected
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1512SP-1 PN
- all versionsaffected
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1514SP F-2 PN
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1514SP-2 PN
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1514SPT F-2 PN
- all versionsaffected
Siemens SIMATIC ET 200SP CPU 1514SPT-2 PN
- all versionsaffected
Siemens SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants)
- all versionsaffected
Siemens SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) V2 CPUs - Windows OS
- all versionsaffected
Same product
siemens: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-63354Affected devices do not properly validate and sanitize visual marker data contained in imported CSV trace files before rendering it on the…37Monitor
- CVE-2026-63353Affected devices do not properly sanitize comment fields contained in imported trace files before rendering them on the Trace page.37Monitor
- CVE-2026-25787Affected devices do not properly validate and sanitize Technology Object (TO) name rendered on the "Motion Control Diagnostics" page of the…37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-25786May 12, 2026 · Affected devices do not properly validate and sanitize PLC/station name rendered on the "communication" parameters page of the web…37Monitor
- ← EarlierCVE-2026-25789May 12, 2026 · Affected devices do not properly validate and sanitize filenames on the Firmware Update page.28Monitor
- Later →CVE-2026-63351Oct 13, 2026 · Affected devices do not properly validate and sanitize visual properties of calculated signals contained in imported CSV trace files before…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-40943217 days apartAffected devices do not properly sanitize contents of trace files.37Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- CVSS9.6 → 9.4
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.