CVE-2019-17326
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 arbitrary file deletion by issuing a HTTP GET request with a specially crafted parameter. 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 versions 1.0.0.527 and earlier contain an arbitrary file deletion vulnerability exploitable via HTTP GET requests with specially crafted parameters. The vulnerability requires user interaction, as the target must visit a malicious web page, suggesting the attack may involve Cross-Site Request Forgery (CSRF) or similar web-based attack vector to trigger the file deletion operation.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Identify REXPERT versionCheck the installed REXPERT version by inspecting the application executable properties (right-click on REXPERT.exe > Properties > Details), the About dialog within the application, or the installer log if available.Affected if Version displayed is 1.0.0.527 or earlier (e.g., 1.0.0.500, 1.0.0.400)
-
Verify HTTP web interface accessibilityCheck if the REXPERT HTTP service is running and accessible by attempting to access the web interface URL (typically http://localhost:port or the configured server address) in a browser or via curl command.Affected if HTTP service is running and responds to requests, indicating the web interface is active
-
Confirm network exposureInspect network configuration to determine if REXPERT HTTP port is bound to all interfaces (0.0.0.0) or is externally accessible, rather than localhost only. Check firewall rules and listening ports using 'netstat -an | grep REXPERT' or similar tools.Affected if The HTTP port is listening on external interfaces or is not restricted by firewall rules
-
Check for CSRF protection mechanismsReview REXPERT web application source or configuration files (if accessible) for presence of anti-CSRF tokens, referer validation, or SameSite cookie attributes. Alternatively, inspect HTTP responses for security headers.Affected if No anti-CSRF tokens or referrer validation is found in state-changing operations
A system is affected if REXPERT version is 1.0.0.527 or earlier AND the HTTP web interface is accessible (locally or over network), since the arbitrary file deletion flaw can be triggered via crafted HTTP GET requests.
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 dataUntil an official patch is available, restrict network access to REXPERT, implement CSRF tokens for all state-changing operations, and apply input validation to ensure file path parameters cannot traverse outside intended directories.
- 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-17326 — 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-17326 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