dbcve.org
RexpertApplication · Clipsoft

CVE-2019-17323

HIGH · 8.8 CVSS v3.1 Published 2019-10-30
Fix available
A fix is available. Upgrade to after 1.0.0.527 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
ClipSoft REXPERT 1.0.0.527 and earlier version allows arbitrary file creation and execution via report print function of rexpert viewer with modified XML document. 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 confidence

ClipSoft REXPERT 1.0.0.527 and earlier versions contain a vulnerability in the report print function where processing a modified XML document allows arbitrary file creation and execution on the target system. The attack requires user interaction, specifically that the target visits a malicious web page, suggesting the vulnerability may be triggered through a client-side attack vector or via specially crafted content loaded in the viewer.

MitigationUpgrade to a patched version of REXPERT when available; until then, restrict user access to untrusted XML documents and educate users about the risks of visiting untrusted web pages.

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
RexpertApplication
Affected:<= 1.0.0.527

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ClipSoft REXPERT installation and version
    Check the installed version of ClipSoft REXPERT by navigating to the program directory (typically in Program Files or Program Files x86), right-clicking the executable file, and viewing its Properties > Details to see the File Version. Alternatively, launch REXPERT and look for the version information in the application's Help > About menu.
    Affected if The installed version is 1.0.0.527 or any version earlier than this release.
  2. Confirm the report print function is present
    Launch REXPERT and navigate through the application's interface to locate the report print or export function. Look for menu options such as File > Print, Report > Print, or similar print-related features that process XML-based report documents.
    Affected if The report print function exists and processes XML documents for output.
  3. Check for XML document handling configuration
    Examine REXPERT's configuration files or settings related to XML report loading. Look for options that control whether the application loads local or remote XML files, or processes XML documents without validation. Check the application's preferences or settings dialog for XML-related processing options.
    Affected if The application can load and process XML documents without requiring valid digital signatures or integrity verification.
  4. Inspect for untrusted content loading mechanisms
    Review any settings or configurations that allow REXPERT to load content from web sources or external URLs. Check if there are options to load reports from web pages, remote servers, or embedded browser components. Look in the application's settings for network, web, or remote content options.
    Affected if REXPERT is configured to load report content from web pages or remote sources that could contain malicious XML.
  5. Audit recent XML report files
    Check the directories where REXPERT stores or caches report templates and XML files. Look for any recently created or modified XML files that may have been opened. On Windows, search for .xml files in REXPERT's user data directories or recent file locations.
    Affected if Unsolicited or modified XML documents have been opened in REXPERT, particularly from untrusted sources.

A user is affected if ClipSoft REXPERT version 1.0.0.527 or earlier is installed, the report print function that processes XML documents is accessible, and the application can load XML content from untrusted or web-based sources without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.0.527
Interim mitigation

Upgrade to a patched version of REXPERT when available; until then, restrict user access to untrusted XML documents and educate users about the risks of visiting untrusted web pages.

Fix this in Rexpert Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-17323 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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