This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Silverstripe
Silverstripe silverstripe/cms through 4.11.0 allows XSS. (2022-11-23, CVE-2022-37421)
In SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR). (2022-06-29, CVE-2022-28803)
SilverStripe Framework through 4.8.1 allows XSS. (2021-10-07, CVE-2021-36150)
In SilverStripe through 4.5, malicious users with a valid Silverstripe CMS login (usually CMS access) can craft profile information which can lead to XSS for other users through specially crafted login form URLs. (2020-07-15, CVE-2020-9311)
SilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user's credentials or other sensitive user input. (2020-02-17, CVE-2019-19325)
In SilverStripe asset-admin 4.0, there is XSS in file titles managed through the CMS. (2019-09-26, CVE-2019-14272)
SilverStripe through 4.3.3 has Flash Clipboard Reflected XSS. (2019-09-25, CVE-2019-12205)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>