ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-40943

Affected devices do not properly sanitize contents of trace files.

Published Mar 10, 2026 · catalog updated Jun 17, 2026 · Affected devices do not

Check if you run it

No confirmed exploitation is on record for CVE-2025-40943. EPSS is 0.48%. Act only if a listed version of Affected devices do not is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Affected devices do not).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.48%
Remediation
Not established
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2025-40943

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-40943. EPSS is 0.48%. Act only if a listed version of Affected devices do not is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-95. EPSS 0.48%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 10, 2026 · NIST NVD

    Detected

    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 t

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 t

Sources

  • CVE.orgVulnerability recordCVE-2025-40943

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-40943

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDVulnerability recordCVE-2025-40943

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.