CVE-2019-19326: SilverStripe Web Cache Poisoning through HTTPRequestBuilder

silverstripe/framework Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Moderate
5.9

CVE-2019-19326: SilverStripe Web Cache Poisoning through HTTPRequestBuilder. Affects silverstripe/framework across 3 version ranges.

>= 3.0.0, < 3.7.5 >= 4.0.0, < 4.4.7 >= 4.5.0, < 4.5.4

Fixed in 3.7.5, 4.4.7 or 4.5.4, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

SilverStripe is an open-source content management system (CMS) framework written in PHP. It provides a flexible and extensible platform for building websites and web applications. The SilverStripe framework, specifically versions 3.0.0 to 3.7.5, 4.0.0 to 4.4.7, and 4.5.0 to 4.5.4, is affected by a web cache poisoning vulnerability through the HTTPRequestBuilder.

Vulnerability Detail

The vulnerability allows an attacker to poison the web cache by manipulating the HTTPRequestBuilder. By exploiting this vulnerability, an attacker can potentially trick the web cache into serving malicious content to unsuspecting users. This can lead to various security risks, including the execution of arbitrary code, unauthorized access to sensitive information, and potential compromise of user sessions.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.0.0, < 3.7.5 3.7.5
    composer require silverstripe/framework:3.7.5
  • >= 4.0.0, < 4.4.7 4.4.7
    composer require silverstripe/framework:4.4.7
  • >= 4.5.0, < 4.5.4 4.5.4
    composer require silverstripe/framework:4.5.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to apply the recommended fix by upgrading to the latest version of the SilverStripe framework.

Conclusion

The SilverStripe framework versions 3.0.0 to 3.7.5, 4.0.0 to 4.4.7, and 4.5.0 to 4.5.4 are vulnerable to web cache poisoning through the HTTPRequestBuilder. It is crucial to upgrade to the latest version of the framework to mitigate the risks associated with this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for silverstripe/framework →

Share this vulnerability

FAQ

SilverStripe is an open-source content management system (CMS) framework written in PHP. It provides a flexible and extensible platform for building websites and web applications.

Web cache poisoning is a technique where an attacker manipulates the content of a web cache to serve malicious or unauthorized content to users.

The risks include the execution of arbitrary code, unauthorized access to sensitive information, and potential compromise of user sessions.

To fix this vulnerability, it is recommended to upgrade to the latest version of the SilverStripe framework.

There is no known workaround for this vulnerability. Upgrading to the latest version of the SilverStripe framework is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for silverstripe/framework.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.0.0, < 3.7.5 3.7.5
    composer require silverstripe/framework:3.7.5
  • >= 4.0.0, < 4.4.7 4.4.7
    composer require silverstripe/framework:4.4.7
  • >= 4.5.0, < 4.5.4 4.5.4
    composer require silverstripe/framework:4.5.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback