Skip to content

Product

silverstripe/framework vulnerabilities

100 published CVES affecting silverstripe/framework, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
100
Critical
3
High
13
Medium
75
Low
3
Unscored
6
CISA KEV
0

Latest silverstripe/framework CVEs

Newest publication first · page 1 of 4

  1. MediumCVSS 5.4 EPSS 0.23% PoC

    Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove SVG data URIs from stored CMS content even though SVG documents can execute script. A CMS author can save such content, and JavaScript executes in the...

  2. MediumCVSS 4.3 EPSS 0.25% PoC

    Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit records through a GridField detail form can send a direct save request that creates a new record even when the user does not have permission to create that record...

  3. MediumCVSS 5.4 EPSS 0.23% PoC

    Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove script-capable XHTML and XML data URIs from stored CMS content. A CMS author can save such content, and JavaScript executes in the browser of another u...

  4. MediumCVSS 5.4 EPSS 0.30% PoC

    Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 5.3.23, bad actor with access to edit content in the CMS could send a specifically crafted encoded payload to the server, which could be used to inject a JavaScript payload on the front end of t...

  5. MediumCVSS 5.4 EPSS 0.33% PoC

    Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. In some cases, form messages can contain HTML markup. This is an intentional feature, allowing links and other relevant HTML markup for the given message. Some form messages include content that the user...

  6. HighCVSS 7.5

    There is a vulnerability whereby arbitrary global functions may be executed if malicious user input is passed through to in the second argument of ViewableData::renderWith. This argument resolves associative arrays as template placeholders. This exploit requires that user code ha...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.