How severe is CVE-2019-19326?

CVE-2019-19326 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2019-19326 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-19326?

CVE-2019-19326 affects Silverstripe. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-19326?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-19326 published?

CVE-2019-19326 was published on 2020-07-15 and last updated on 2026-06-17.

CVE-2019-19326

CVE-2019-19326 is a medium-severity vulnerability in Silverstripe with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-444.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v2: 4.3
EPSS exploit prediction: 1% (51st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-444
Affected product: Silverstripe
Published: 2020-07-15
Last modified: 2026-06-17

Description

Silverstripe CMS sites through 4.4.4 which have opted into HTTP Cache Headers on responses served by the framework's HTTP layer can be vulnerable to web cache poisoning. Through modifying the X-Original-Url and X-HTTP-Method-Override headers, responses with malicious HTTP headers can return unexpected responses to other consumers of this cached response. Most other headers associated with web cache poisoning are already disabled through request hostname forgery whitelists.

Frequently asked questions

What is CVE-2019-19326?: Silverstripe CMS sites through 4.4.4 which have opted into HTTP Cache Headers on responses served by the framework's HTTP layer can be vulnerable to web cache poisoning. Through modifying the X-Original-Url and X-HTTP-Method-Override headers, responses with malicious HTTP headers can return unexpected responses to other consumers of this cached response. Most other headers associated with web cache poisoning are already disabled through request hostname forgery whitelists.
How severe is CVE-2019-19326?: CVE-2019-19326 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2019-19326 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-19326?: CVE-2019-19326 affects Silverstripe. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-19326?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-19326 published?: CVE-2019-19326 was published on 2020-07-15 and last updated on 2026-06-17.

References

https://www.silverstripe.org/download/security-releases/CVE-2019-19326

Affected products (1)

cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*

More vulnerabilities in Silverstripe

CVE-2007-2321 — Critical (CVSS 10.0): Unspecified vulnerability in the search functionality in SilverStripe 2.0.0 has unknown impact and attack vectors.
CVE-2019-12204 — Critical (CVSS 9.8): In SilverStripe through 4.3.3, a missing warning about leaving install.php in a public webroot can lead to…
CVE-2019-5715 — Critical (CVSS 9.8): All versions of SilverStripe 3 prior to 3.6.7 and 3.7.3, and all versions of SilverStripe 4 prior to 4.0.7, 4.1.5,…
CVE-2019-12437 — High (CVSS 8.8): In SilverStripe through 4.3.3, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in…
CVE-2020-6164 — High (CVSS 7.5): In SilverStripe through 4.5.0, a specific URL path configured by default through the silverstripe/framework module can…
CVE-2020-9280 — High (CVSS 7.5): In SilverStripe through 4.5, files uploaded via Forms to folders migrated from Silverstripe CMS 3.x may be put to the…

All CVEs affecting Silverstripe →

Other CWE-444 (HTTP Request/Response Smuggling) vulnerabilities

CVE-2025-1867 — Critical (CVSS 10.0): Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in ithewei libhv allows…
CVE-2022-22536 — Critical (CVSS 10.0): SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53…
CVE-2018-3907 — Critical (CVSS 10.0): An exploitable vulnerability exists in the REST parser of video-core's HTTP server of the Samsung SmartThings Hub…
CVE-2025-55315 — Critical (CVSS 9.9): Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows an authorized…
CVE-2020-15049 — Critical (CVSS 9.9): An issue was discovered in http/ContentLengthInterpreter.cc in Squid before 4.12 and 5.x before 5.0.3. A Request…
CVE-2026-13763 — Critical (CVSS 9.8): Inconsistent interpretation of HTTP/2 requests in AWS Application Load Balancer with AWS WAF enabled might allow remote…

Browse all CWE-444 (HTTP Request/Response Smuggling) vulnerabilities →