CriticalCVE-2019-13608

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

    Published In CISA KEV since Sources: CVE.org

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Citrix StoreFront Server to version 1903, Citrix StoreFront Server to version 3.12.4000, Citrix StoreFront Server to version 3.0.8000. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Citrix StoreFront Server lt 1811..1903
    • Citrix StoreFront Server lt *..3.12.4000
    • Citrix StoreFront Server lt *..3.0.8000
    Fixed in
    • Citrix StoreFront Server 1903
    • Citrix StoreFront Server 3.12.4000
    • Citrix StoreFront Server 3.0.8000

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    30.0 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 98.2

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    239.66 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    30.0 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    98.2
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 4 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-611

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable without authentication or user interaction and lets an attacker read sensitive data off the server. Its value to attackers lies in reconnaissance and credential theft rather than direct code execution. CISA flags it as used in ransomware campaigns, and its exploitation likelihood is rated very high. Citrix access infrastructure is a favoured initial-access vector for ransomware operators because it is often internet-facing and brokers access to the whole VDI estate. Treat an internet-exposed, unpatched StoreFront server as critical and fix it within 24 hours. An internal-only server with tight egress controls can be scored high and handled in the next maintenance window. The end-of-life status of the affected LTSR branches adds further weight to migrating promptly.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Enumerate every StoreFront server, including all nodes in each server group. Confirm the installed version via Programs and Features or Get-STFVersion in the StoreFront PowerShell SDK. Vulnerable builds are anything before 1903, 7.15 LTSR before CU4 (3.12.4000), and 7.6 LTSR before CU8 (3.0.8000).
      • Patch: Upgrade to at least 1903, 7.15 LTSR CU4 (3.12.4000) or 7.6 LTSR CU8 (3.0.8000). Both LTSR branches are now out of support, so move straight to a currently supported StoreFront LTSR release. Look up the exact version in the Citrix advisory. In server groups, upgrade the primary node first, then propagate changes.
      • Cut exposure: Any StoreFront instance reachable directly from the internet on TCP 80/443 without a gateway in front should be placed behind Citrix Gateway/ADC or firewalled to internal ranges until patched.
      • Block egress: Restrict outbound HTTP/HTTPS/FTP and external DNS resolution from StoreFront hosts to what is operationally required. XXE exploitation usually exfiltrates data out-of-band.
      • Compromise assessment: Review IIS, proxy and firewall logs for the past months (see Detection). If anything looks suspicious, rotate every secret stored in files the IIS app pool can read, such as service-account passwords, certificate private keys and Delivery Controller bindings. Then hunt for lateral movement towards domain controllers and the XenApp/XenDesktop estate.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Put StoreFront in a dedicated DMZ or server VLAN. Allow inbound traffic only from the Gateway/ADC SNIP and internal clients. Allow outbound traffic only to Delivery Controllers (XML service, TCP 80/443), domain controllers and defined update targets. Deny and log everything else.
      • WAF/IPS: Enable XML security checks in Citrix Web App Firewall or your upstream WAF. Block request bodies to /Citrix/ paths that contain <!DOCTYPE, <!ENTITY, SYSTEM " or PUBLIC ", since legitimate StoreFront clients do not send DTDs. Suricata/Snort idea: content:"<!ENTITY"; nocase; http_client_body; content:"SYSTEM"; nocase; distance:0; on HTTP traffic to the StoreFront VIP. This requires TLS termination at the sensor or ADC.
      • Endpoint hardening: Run the store IIS app pools under a minimally privileged identity. Tighten NTFS read rights so web.config, backups and scripts holding cleartext credentials are not readable via XXE.
      • IAM / least privilege: Make sure controller-binding service accounts hold no domain-admin rights. Move cleartext secrets off the box into a vault or gMSA.
      • Configuration: Disable unused stores, legacy PNAgent sites and plain HTTP bindings (TCP 80) to shrink the attack surface.

    3. Runbook step 3

      Detection rules

      • Network telemetry (Zeek/firewall): Outbound HTTP, FTP or DNS from StoreFront hosts to unknown external destinations is a strong out-of-band XXE signal. Zeek idea: conn.log where id.orig_h in storefront_hosts and not id.resp_h in allowlist. Fetches of .dtd files in http.log are particularly telling.
      • Sysmon EID 3 / EID 22: w3wp.exe on StoreFront making network connections or DNS queries to non-internal destinations. KQL: DeviceNetworkEvents | where DeviceName in (sf_hosts) and InitiatingProcessFileName =~ "w3wp.exe" and RemoteIPType == "Public".
      • IIS access logs: Bursts of POSTs to /Citrix/* from external IPs with unusual content types or sizes and no preceding normal logon flow. Also watch for HTTP 500 spikes on store endpoints. SPL: index=iis host=storefront* cs_method=POST cs_uri_stem="/Citrix/*" sc_status=500 | stats count by c_ip.
      • WAF/ADC logs: Hits on XML checks or body signatures containing <!ENTITY/<!DOCTYPE. Sigma shape: logsource: category: webserver/waf, detection: request_body|contains: ['<!ENTITY', 'SYSTEM "file:'].
      • Follow-on activity: StoreFront service accounts logging on from unexpected hosts (Windows EID 4624, logon type 3/10), and new services or scheduled tasks on Citrix infrastructure (EID 7045/4698), indicating reuse of harvested credentials.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: cvelistv5, NVD (NIST), CISA KEV Catalog

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    citrixstorefront_server
    • 1811 – < 1903
    • < 3.12.4000
    • < 3.0.8000
    • 1903
    • 3.12.4000
    • 3.0.8000

    Vendors and products

    Weakness classes (CWE)

    • CWE-611Improper Restriction of XML External Entity Reference

      Base

      The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

      Entry at MITRE CWE-611

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • support.citrix.comarticle/CTX251988x_refsource_CONFIRM, Mitigation, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2019-13608government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2019-13608
    <a href="https://intel.neosec.eu/en/cve/CVE-2019-13608"><img src="https://intel.neosec.eu/badge/cve/CVE-2019-13608.svg?lang=en" alt="CVE-2019-13608 – NEOSEC Intel" height="20"></a>