CVE-2019-13608
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 · uneditedCitrix StoreFront Server before 1903, 7.15 LTSR before CU4 (3.12.4000), and 7.6 LTSR before CU8 (3.0.8000) allows XXE attacks.
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 confidenceCitrix StoreFront Server contains an XML External Entity (XXE) vulnerability in versions before 1903, 7.15 LTSR CU4, and 7.6 LTSR CU8. The vulnerability allows attackers to inject malicious XML entities into requests processed by the StoreFront Server, potentially enabling disclosure of internal files, denial of service, or server-side request forgery.
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>= 1811, < 1903< 3.12.4000< 3.0.8000CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify Citrix StoreFront Server versionOpen the StoreFront Management Console and navigate to the About section, or use the Get-STFRole cmdlet via PowerShell to retrieve the installed version numberAffected if The version falls within these ranges: 1811 through any version before 1903, or any version before 3.12.4000 (which maps to 7.15 LTSR CU4), or any version before 3.0.8000 (which maps to 7.6 LTSR CU8)
-
Confirm StoreFront services are runningCheck that the Citrix StoreFront Service (Citrix StoreFront) or the StoreFront Service Host is running on the server via Services.msc or PowerShellAffected if The service is running and the version is in the affected ranges from step 1
-
Identify if XML-based endpoints are exposedReview the StoreFront website bindings and virtual directories in IIS Manager. Look for paths such as /Citrix/Store or /PowerShellRemoting that accept XML-formatted requestsAffected if XML-handling endpoints are accessible and the StoreFront version is vulnerable
-
Review XML parser configurationExamine the web.config files in the StoreFront installation directory (typically under C:\inetpub\wwwroot\Citrix\StoreFront) for custom XML parser settings that may control external entity resolutionAffected if XML parser is configured to allow external entity resolution and the version is in the affected range
You are affected if the installed Citrix StoreFront Server version is 1811 or later but earlier than 1903, or earlier than 3.12.4000, or earlier than 3.0.8000, and the server processes XML 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.
dbcve · scoped3.0.80003.12.40001903
Upgrade Citrix StoreFront Server to version 1903, 7.15 LTSR CU4 (3.12.4000), or 7.6 LTSR CU8 (3.0.8000) or later. If immediate patching is not possible, disable XML entity resolution in the XML parser configuration.
1903 (current release) or 3.12.4000 (7.15 LTSR CU4) or 3.0.8000 (7.6 LTSR CU8)
- 1. Identify the current Citrix StoreFront Server version by checking Add/Remove Programs or the StoreFront management console
- 2. Determine which release branch you are on: current release (1808-1902), 7.15 LTSR, or 7.6 LTSR
- 3. For StoreFront versions 1811 through 1902: Download and install StoreFront 1903 or later from support.citrix.com
- 4. For StoreFront 7.15 LTSR (versions before 3.12.4000): Download and install Cumulative Update 4 (3.12.4000) or later from support.citrix.com
- 5. For StoreFront 7.6 LTSR (versions before 3.0.8000): Download and install Cumulative Update 8 (3.0.8000) or later from support.citrix.com
- 6. Apply the upgrade following Citrix StoreFront upgrade documentation (backup configuration, run installer, verify services)
- 7. Verify the upgrade was successful by checking the StoreFront version and confirming XML parsing functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13608 — 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-13608 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