CVE-2019-19164
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 · unediteddext5.ocx ActiveX Control in Dext5 Upload 5.0.0.112 and earlier versions contains a vulnerability that could allow remote files to be executed by setting the arguments to the activex method. A remote attacker could induce a user to access a crafted web page, causing damage such as malicious code infection.
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 confidenceThe dext5.ocx ActiveX control in Dext5 Upload versions 5.0.0.112 and earlier contains a vulnerability allowing remote file execution. Attackers can exploit this by tricking users into visiting crafted web pages that invoke the ActiveX method with malicious arguments, leading to arbitrary code execution on the victim's machine.
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= 2.7CVSS 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.1/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.
-
Locate dext5.ocx on the systemSearch for dext5.ocx in common Windows system directories such as C:\Windows\System32, C:\Windows\SysWOW64, or search the entire system using: dir /s /b C:\dext5.ocx or Get-ChildItem -Path C:\ -Filter dext5.ocx -Recurse -ErrorAction SilentlyContinueAffected if The dext5.ocx file exists on the system and its version matches 2.7 or falls within 5.0.0.112 and earlier versions if other version information is available
-
Identify installed Dext5 Upload versionCheck the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Dext5 or Raonwiz Dext5, and read the DisplayVersion value. Alternatively, right-click the dext5.ocx file if found, select Properties, and view the Details tab for version information.Affected if The installed version is 2.7, or the version shown is 5.0.0.112 or any earlier version number
-
Verify ActiveX control registrationOpen Internet Explorer, go to Tools > Manage Add-ons, and look for dext5.ocx in the list of ActiveX controls. Alternatively, check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Code Store Database\Distribution Units for dext5.ocx entries.Affected if The dext5.ocx ActiveX control is listed as installed or enabled in browser add-ons
-
Check for browser zone security settings allowing ActiveXIn Internet Explorer, go to Internet Options > Security > Custom Level, and review settings under ActiveX controls and plugins. Look for 'Run ActiveX controls and plugins' and 'Script ActiveX controls marked safe for scripting' to see if they are enabled for affected zones.Affected if ActiveX controls are permitted to run in any browser zone (Internet, Intranet, or Trusted Sites) where users may encounter malicious web pages
A user is affected if dext5.ocx is present on their system AND the installed Dext5 Upload version is 2.7 or any version at or below 5.0.0.112, with ActiveX execution allowed in their browser environment.
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 Dext5 Upload to a version newer than 5.0.0.112, or disable the dext5.ocx ActiveX control and restrict ActiveX execution in affected browsers as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19164 — 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-19164 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