CVE-2017-14759
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 · uneditedOpenText Document Sciences xPression (formerly EMC Document Sciences xPression) v4.5SP1 Patch 13 (older versions might be affected as well) is prone to an XML External Entity vulnerability: /xFramework/services/QuickDoc.QuickDocHttpSoap11Endpoint/. An unauthenticated user is able to read directory listings or system files, or cause SSRF or Denial of Service.
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 confidenceThis is an XML External Entity (XXE) vulnerability in OpenText Document Sciences xPression's SOAP endpoint (/xFramework/services/QuickDoc.QuickDocHttpSoap11Endpoint/). An unauthenticated attacker can craft malicious XML payloads with external entity references to read arbitrary files from the server's filesystem, perform SSRF attacks against internal infrastructure, or cause denial of service.
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<= 4.5CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Confirm OpenText Document Sciences xPression is installedLocate the xPression installation directory and identify the version from installation manifests, About dialogs, or version files in the application rootAffected if The application is installed and the version is 4.5 or lower
-
Check if the SOAP endpoint is exposedAttempt to access the URL path /xFramework/services/QuickDoc.QuickDocHttpSoap11Endpoint/ via HTTP or HTTPS from the server or a test clientAffected if The endpoint responds with a SOAP service description or accepts SOAP requests
-
Identify the installed version numberCompare your installed xPression version against the affected range <= 4.5 using the application's version informationAffected if The installed version is 4.5 or any version lower than 4.5
-
Verify XML external entity processing is enabledSend a benign XXE probe payload to the SOAP endpoint with an external entity reference to test if the parser resolves itAffected if The application parses external entities and returns data from the referenced external source or shows XXE error behavior
A user is affected if OpenText Document Sciences xPression version 4.5 or lower is installed and the /xFramework/services/QuickDoc.QuickDocHttpSoap11Endpoint/ SOAP endpoint is accessible with XML external entity processing enabled.
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 external entity processing in the XML parser configuration for the affected SOAP endpoint, apply input validation on XML submissions, and update to a patched version if available. Consider network segmentation to limit potential SSRF impact.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14759 — 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-2017-14759 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