SilverStripe Web Cache Poisoning through HTTPRequestBuilder

published 2020-07-15 6 y ago modified 2026-06-17 4 mo ago also GHSA-q9ff-3q93-fm8m , EUVD-2022-4928

cvss: 5.9; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 links 3

packagist silverstripe/framework 3.7.5, 4.4.7, 4.5.4
silverstripe silverstripe 3.7.5, 4.4.7, 4.5.4

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	silverstripe/framework	>=4.0.0, <4.4.7 >=4.5.0, <4.5.4 >=3.0.0, <3.7.5	4.4.7 4.5.4 3.7.5

Classification

Weakness

CWE-444 Inconsistent Interpretation of HTTP Requests

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary