CVE-2025-0694
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient path validation in CODESYS Control allows low privileged attackers with physical access to gain full filesystem access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCODESYS Control contains an insufficient path validation vulnerability (likely path traversal) that allows low-privileged attackers with physical access to escape directory restrictions and gain full filesystem access, enabling read/write of sensitive files, configuration data, and potentially executable code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm CODESYS Control installationLocate CODESYS Control installation directory (commonly in C:\Program Files\CODESYS or C:\Program Files (x86)\CODESYS on Windows, or /opt/codesys on Linux). Verify the presence of the CODESYS Control runtime components and configuration files.Affected if CODESYS Control is not installed on the system.
-
Identify installed CODESYS Control versionCheck the version of CODESYS Control by examining the installation's version metadata. On Windows, right-click the main executable (such as CODESYSControl.exe) and view Properties > Details, or run the CODESYS installer with version query flags. On Linux, check the installed RPM/DEB package or examine version files in the installation directory.Affected if The installed version cannot be determined or is older than the patched version.
-
Verify file access functionality is enabledInspect CODESYS Control configuration files (typically with .cfg or .xml extensions in the installation directory or AppData folder) for settings related to file system access, path handling, or file transfer features. Look for parameters enabling WebVisu, file browsing, or external file operations.Affected if File access or path handling features are enabled in the configuration.
-
Examine directory restriction settingsReview CODESYS Control runtime configuration for any defined file access restrictions, sandboxing settings, or directory confinement parameters. Check if the system enforces limited filesystem access boundaries for the runtime process.Affected if No directory restrictions are configured, or restrictions rely solely on built-in path validation without vendor patches.
-
Assess physical access controlsEvaluate physical security controls on the host running CODESYS Control. Determine whether low-privileged users or unauthorized personnel can directly access the hardware, console, or removable media ports.Affected if Physical access to the control system is not restricted to trusted personnel.
The environment is affected if CODESYS Control is installed with a version prior to the vendor patch, has file access or path handling features enabled, and the system is physically accessible to low-privileged users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches when available; restrict physical access to control systems; implement strict file system permissions and input validation; consider compensating controls like network segmentation and monitoring.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0694 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data