CVE-2025-56814
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 · uneditedA code injection vulnerability in the wxExecute() function of OpenCPN v5.12.0 allows attackers to execute arbitrary code via embedding shell metacharacters.
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 confidenceOpenCPN v5.12.0 contains a code injection vulnerability in the wxExecute() function that allows attackers to execute arbitrary code by embedding shell metacharacters in input, leading to high-severity arbitrary code execution.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 OpenCPN installation and locate binaryCheck common installation paths: Windows (C:\Program Files\OpenCPN\opencpn.exe), Linux (/usr/bin/opencpn, /usr/local/bin/opencpn), macOS (/Applications/OpenCPN.app/Contents/MacOS/opencpn). Run 'which opencpn' on Linux/macOS or check Add/Remove Programs on Windows.Affected if OpenCPN is installed and the executable exists on the system
-
Determine installed OpenCPN versionRun 'opencpn --version' or 'opencpn -V' from command line, or right-click the executable and select Properties > Details on Windows to view the File Version.Affected if Version is 5.12.0 or falls within the affected range prior to patch
-
Identify wxExecute usage in OpenCPN configuration or pluginsSearch OpenCPN user data directories (typically ~/.opencpn/ on Linux/macOS, %APPDATA%\OpenCPN on Windows) for any plugin .dll/.so files or configuration files that may contain custom scripts or command execution paths. Also inspect any user-installed plugins for wxExecute calls.Affected if A plugin or configuration file contains wxExecute calls that could accept external input
-
Audit user-accessible input paths that could reach wxExecuteReview any OpenCPN plugins, scripts, or configuration options that process external input (such as route imports, NMEA data feeds, or external chart paths) and check if they invoke wxExecute without sanitization.Affected if User-supplied data from file imports, network feeds, or plugin APIs can reach a wxExecute call without shell metacharacter filtering
If OpenCPN v5.12.0 or an unpatched version is installed AND any wxExecute calls process user-supplied input without sanitization, the system is vulnerable to arbitrary code execution.
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 dataUpgrade to a patched version of OpenCPN. Until then, identify all wxExecute() calls accepting user-supplied input and implement strict input validation/sanitization to remove shell metacharacters, or refactor to use safer alternatives that avoid shell invocation.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56814 — 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-56814 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