CVE-2019-17325
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 · uneditedClipSoft REXPERT 1.0.0.527 and earlier version allows remote attacker to upload arbitrary local file via the ActiveX method in RexViewerCtrl30.ocx. That could lead to disclosure of sensitive information. User interaction is required to exploit this vulnerability in that the target must visit a malicious web page.
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 confidenceClipSoft REXPERT 1.0.0.527 and earlier contains an ActiveX control (RexViewerCtrl30.ocx) that allows remote attackers to upload arbitrary local files from the victim's system. This is achieved through a malicious web page requiring user interaction, leading to disclosure of sensitive information.
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<= 1.0.0.527CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Verify REXPERT installation existsCheck for REXPERT installation directory, typically in C:\Program Files\ClipSoft\REXPERT or C:\Program Files (x86)\ClipSoft\REXPERT. Also check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for REXPERT entry.Affected if REXPERT software is found installed on the system.
-
Determine installed REXPERT versionLocate the main executable (REXPERT.exe) in the installation directory, right-click and select Properties, or check the Uninstall registry entry for the DisplayVersion value. Compare the version number to 1.0.0.527 or earlier.Affected if The installed version is 1.0.0.527 or lower.
-
Locate vulnerable ActiveX control fileSearch for RexViewerCtrl30.ocx file on the system. Common paths include the REXPERT installation directory, Windows\System32, or Windows\SysWOW64. Use command: dir /s C:\RexViewerCtrl30.ocxAffected if The file RexViewerCtrl30.ocx is present on the system.
-
Check if ActiveX control is registeredOpen Windows Registry and check HKLM\SOFTWARE\Classes\CLSID for the CLSID associated with RexViewerCtrl30.ocx, or run regsvr32 to query registration status. Also check Internet Explorer add-ons.Affected if The ActiveX control is registered and enabled in the system.
A system is affected if ClipSoft REXPERT version 1.0.0.527 or earlier is installed with the RexViewerCtrl30.ocx ActiveX control present and registered.
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 dataDisable or restrict the RexViewerCtrl30.ocx ActiveX control in Internet Explorer and browser security zones, and update REXPERT to the latest patched version once available from the vendor.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17325 — 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-17325 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