cve.bz

CVE-2025-0694 codesys: Path traversal

6.6 mediumEPSS 0.3%

Medium (6.6) in codesys. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Insufficient path validation in CODESYS Control allows low privileged attackers with physical access to gain full filesystem access.

Severity

CVSS 3.1

6.6 medium
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-03-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-0694 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-0694?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-0694?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-0694 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
CODESYS Control for BeagleBone SLbefore 4.16.0.0
CODESYS Control for emPC-A/iMX6 SLbefore 4.16.0.0
CODESYS Control for IOT2000 SLbefore 4.16.0.0
CODESYS Control for Linux ARM SLbefore 4.16.0.0
CODESYS Control for Linux SLbefore 4.16.0.0
CODESYS Control for PFC100 SLbefore 4.16.0.0
CODESYS Control for PFC200 SLbefore 4.16.0.0
CODESYS Control for PLCnext SLbefore 4.16.0.0
CODESYS Control for Raspberry Pi SLbefore 4.16.0.0
CODESYS Control for WAGO Touch Panels 600 SLbefore 4.16.0.0
CODESYS Control RTE (for Beckhoff CX) SLbefore 3.5.21.0
CODESYS Control RTE (SL)before 3.5.21.0
CODESYS Control Win (SL)before 3.5.21.0
CODESYS Runtime Toolkitbefore 3.5.21.0
CODESYS Virtual Control SLbefore 4.16.0.0

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-076-01CODESYS in Festo Automation Suite2026-02-26Critical ManufacturingFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.0, Festo Automation Suite <2.8.0.138 installed with CODESYS Development System 3.5.16.10, Festo Automation Suite 2.8.0.137 installed with CODESYS Development System 3.0 and 1 moreCODESYS Development System 3.5.21.20 external component of Festo Automation Suite 2.8.0.138

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON