CVE-2018-19011
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 · uneditedCX-Supervisor (Versions 3.42 and prior) can execute code that has been injected into a project file. An attacker could exploit this to execute code under the privileges of the application.
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 · high confidenceCX-Supervisor versions 3.42 and prior contain a code injection vulnerability in project file parsing. An attacker can embed malicious code within a project file, which the application will execute when the file is loaded, allowing arbitrary code execution under the application's privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.42CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Check if CX-Supervisor is installedLook for CX-Supervisor in the Windows installed programs list via Control Panel > Programs and Features, or check for the installation directory (typically in C:\Program Files\Omron\CX-Supervisor or similar locations)Affected if CX-Supervisor is present on the system
-
Determine the installed CX-Supervisor versionRight-click the CX-Supervisor executable (usually named CX-Supervisor.exe) in the installation folder, select Properties, then go to the Details tab to view the File VersionAffected if The version displayed is 3.42 or lower
-
Locate project files that may have been loadedSearch for .cxp and .cxs project files on the system (typical locations include user documents, project folders, or the CX-Supervisor workspace directory)Affected if Project files exist and have been opened or loaded in CX-Supervisor
-
Inspect project file origin and integrityExamine the source of any .cxp/.cxs files - check file properties for the creator, review how the file was obtained (received via email, downloaded, or from external media), and verify the file hash if a known-good baseline existsAffected if project files originate from untrusted or external sources, or their integrity cannot be verified
If CX-Supervisor version 3.42 or lower is installed AND project files from untrusted sources have been loaded, the environment may be affected by this vulnerability.
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 CX-Supervisor to a version newer than 3.42. If upgrading is not immediately feasible, implement strict controls on project file sources and validate all project files before loading.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19011 — 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-2018-19011 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