Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA siemens

CVE-2026-63356: Affected devices do not properly sanitize calculated signal names contained in imported CSV trace files before including them in error messa

Noroxi assessment

Priority: Monitor (action score 21/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.18% (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 sanitize calculated signal names contained in imported CSV trace files before including them in error messages on the Trace page. 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. Attacker-controlled JavaScript could be executed in the user’s browser session when the resulting error message is displayed.

MediumCVSS 5.3 · v4.0—No exploit No fix recorded
Published
Oct 13, 2026
Updated
Oct 15, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · siemens
6.1
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:L/I:L/A:N

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.

Follow CVE-2026-63356

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

—

Limit the impact of XSS

This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.

Check security headers

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

Other 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 T
    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-63350Affected devices do not properly restrict executable content contained in imported trace files.
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-63352Oct 13, 2026 · Affected devices do not properly sanitize calculated signal data contained in imported CSV trace files before rendering it on the Trace page
    21Monitor
  • ← EarlierCVE-2026-63355Oct 13, 2026 · Affected devices do not properly sanitize signal names contained in imported CSV trace files before rendering them in selection menus on the
    21Monitor
  • Later →CVE-2026-63357Oct 13, 2026 · Affected devices do not properly sanitize calculated signal data contained in imported calculated signal files before rendering it on the Tr
    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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-633530 days apartAffected devices do not properly sanitize comment fields contained in imported trace files before rendering them on the Trace page.
    37Monitor
  • CVE-2026-633540 days apartAffected devices do not properly validate and sanitize visual marker data contained in imported CSV trace files before rendering it on the T
    37Monitor
  • CVE-2026-25786154 days apartAffected devices do not properly validate and sanitize PLC/station name rendered on the "communication" parameters page of the web interface
    37Monitor
  • CVE-2026-25787154 days apartAffected devices do not properly validate and sanitize Technology Object (TO) name rendered on the "Motion Control Diagnostics" page of the
    37Monitor
  • CVE-2026-25789154 days apartAffected devices do not properly validate and sanitize filenames on the Firmware Update page.
    28Monitor
  • CVE-2026-633510 days apartAffected devices do not properly validate and sanitize visual properties of calculated signals contained in imported CSV trace files before
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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
P
Scope
X

CVSS vector

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

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Change log

  1. SSVC exploitation— → none
  2. Exploit maturity— → none
  3. CVSS6.1 → 5.3

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records