CVE-2019-19166
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 · uneditedTobesoft XPlatform v9.1, 9.2.0, 9.2.1 and 9.2.2 have a vulnerability that can load unauthorized DLL files. It allows attacker to cause remote code execution.
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 confidenceTobesoft XPlatform versions 9.1, 9.2.0, 9.2.1, and 9.2.2 contain a DLL planting/hijacking vulnerability where the application loads unauthorized DLL files from insecure paths. An attacker can place a malicious DLL in a location from which XPlatform loads libraries, achieving remote code execution when the application runs.
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= 9.1= 9.2.0= 9.2.1= 9.2.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify XPlatform installation locationSearch for 'XPlatform' or ' Nexacro' directories in Program Files (C:\Program Files, C:\Program Files (x86)) and common application directories. Also check for 'nxruntimemodule' or 'nxcore' related files.Affected if XPlatform is installed and the vulnerable DLL loading behavior is present in the application directory structure.
-
Determine installed XPlatform versionRight-click the main executable (commonly named nxruntimemodule.exe or similar XPlatform-related .exe), select Properties, and check the File Version in the Details tab. Alternatively, look for version info in the installation directory or uninstall registry entry.Affected if The installed version matches 9.1, 9.2.0, 9.2.1, or 9.2.2.
-
Verify insecure DLL search path behaviorRun the XPlatform application while monitoring DLL loads using Process Monitor (ProcMon) from Sysinternals. Filter by the XPlatform process name and look for DLLs loaded from user-writable directories (temp folders, application directory, working directory).Affected if The application loads DLLs from the same directory as the executable or from paths writable by non-privileged users.
-
Check for unprotected DLL loading locationsExamine the XPlatform installation directory for world-writable permissions. Right-click the folder, go to Properties > Security, and verify that standard users cannot write files to the application directory or subdirectories.Affected if The XPlatform installation directory or its subdirectories have write permissions for standard users, allowing an attacker to place a malicious DLL.
-
Inspect application working directoryLaunch XPlatform from a different working directory (e.g., from Desktop) and use Process Monitor to check if the application attempts to load DLLs from the current working directory rather than using absolute paths.Affected if The application loads DLLs from the current working directory or does not use fully qualified paths for DLL loading.
A system is affected if Tobesoft XPlatform version 9.1, 9.2.0, 9.2.1, or 9.2.2 is installed and the application directory or its DLL search paths are writable by untrusted users, enabling DLL hijacking.
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 dataRestrict DLL loading by using absolute paths, implementing DLL whiteligning, enabling Safe DLL Search Mode, and/or upgrading to a patched version if available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19166 — 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-2019-19166 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