Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2019-19326
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 05:05 UTC · Revision 1
Source evidence
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.
osv:CVE-2019-19326
Complete source record
{
"id": "828ff6033d6237dde0de8eb1a3def8569a724b032385d8f4dde3d08a83438ba4",
"url": "https://osv.dev/vulnerability/CVE-2019-19326",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2019-19326",
"summary": "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.",
"evidence": "osv:CVE-2019-19326",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2019-19326",
"aliases": [
"CVE-2019-19326",
"GHSA-q9ff-3q93-fm8m"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/silverstripe/silverstripe-framework",
"type": "GIT",
"events": [
{
"introduced": "bfa436bb2a6f4534e82130dda38b625f25634578"
},
{
"fixed": "f2b8946407b7f44d09dd3bbccadb3db4e30357f7"
},
{
"introduced": "6d8df46b8a7e3281fbd1299c626dd7a5a9a14a83"
},
{
"fixed": "f2d9150755aef32f7bc7aa6b5321d966f6540af7"
},
{
"introduced": "f75094abcd8ff29ece4bca05a297fda106e3ba89"
},
{
"fixed": "1726cd1f9757ec2ea503a116064d87441950abfc"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.7.5"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.0.0"
},
{
"fixed": "4.4.7"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.5.0"
},
{
"fixed": "4.5.4"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2019-19326.json"
}
}
],
"modified": "2026-10-24T10:30:24.515002431Z",
"provider": "osv",
"references": [
"https://www.silverstripe.org/download/security-releases/CVE-2019-19326"
],
"provider_metadata": {
"unresolved_ranges": [
{
"cpes": [
"cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*"
],
"vendor_product": "silverstripe:silverstripe",
"extracted_events": [
{
"range": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.7.5"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.4.7"
},
{
"introduced": "4.5.0"
},
{
"fixed": "4.5.4"
}
],
"source": "CPE_RANGE"
}
]
}
]
}
},
"related_cves": [
{
"value": "CVE-2019-19326",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 431167,
"published_at": "2020-07-15T19:15:11.18+00:00"
}