# CVE-2019-13608: Citrix StoreFront Server XML External Entity (XXE) Processing

> An attacker can exploit an XML External Entity vulnerability in Citrix StoreFront Server to read sensitive files or cause denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-22h8-5mmq-pgx3

## What is CVE-2019-13608?

CVE-2019-13608 is a high-severity vulnerability in n/a, published on 29 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Citrix StoreFront Server before 1903, 7.15 LTSR before CU4 (3.12.4000), and 7.6 LTSR before CU8 (3.0.8000) allows XXE attacks.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2019-13608?

It affects 1 product.


Products: Citrix Storefront Server.

## How do I fix CVE-2019-13608?

No fix has been published for CVE-2019-13608 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-13608 being exploited?

Yes. Attackers have exploited CVE-2019-13608 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- Citrix StoreFront Server - XML External Entity (nuclei): http/cves/2019/CVE-2019-13608.yaml

## Other vulnerabilities in n/a

- [CVE-2020-8200](https://insights.sbomify.com/CVE-2020-8200/): Information disclosure in Citrix StoreFront (medium 6.5)
- [CVE-2022-27503](https://insights.sbomify.com/CVE-2022-27503/): Cross-site scripting in StoreFront (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13608 and fix it if it is affected.

What it is: CVE-2019-13608 is a high-severity vulnerability in n/a, published on 29 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-13608 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13608/ (Markdown: https://insights.sbomify.com/CVE-2019-13608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13608
- OSV: https://osv.dev/vulnerability/CVE-2019-13608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13608/
Summaries are generated and may contain mistakes; the official description above is the record.