Introduction:
=============
SilverStripe CMS is an open source web content management system used by governments, businesses,
and non-profit organisations around the world. It is a power tool for professional web development teams,
and web content authors rave about how easy it is to use.

As a platform, SilverStripe CMS is used to build websites, intranets, and web applications. The modern
architecture of SilverStripe CMS allows organisations to keep pace with innovation on the web. SilverStripe
CMS enables websites and applications to contain stunning design, great content, and compelling interactive
and social functions.

SilverStripe CMS is open source, underpinned by public documentation, free code, and a developer community.
It is based on open standards and supports multiple technology platforms. SilverStripe CMS is built and
commercially supported by SilverStripe Ltd., a software company responsible for ensuring innovation, focus,
and quality in the software. SilverStripe Ltd., its Partners around the world, and the global SilverStripe
Developer Network provide commercial services around designing, implementing, and customising websites and
applications based on SilverStripe CMS.

The vulnerability is located in the `Print` module of the groups and roles settings function when processing to request via
POST method manipulated `first & lastnames`. Remote attackers can include a new role bound to an user configuration with own
injected script code (payload). The injected context will be executed in the edit id list and the main index role/groups list.

The vulnerability is located in the `message validation` module when processing to request via POST method manipulated
`CEO` or `Revenue` parameters. The injected script code will be stored in the users profile of the company. The code gets
executed by in the user profile company.

Exploitation of the persistent web vulnerability requires low user interaction and a local low privileged web-application
user account with a password. Successful exploitation of the vulnerability can lead to persistent session hijacking (customers),
account steal via persistent web attacks, persistent phishing or or persistent manipulation of vulnerable module context.

Disclaimer:
===========
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties,
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases
or trade with fraud/stolen material.

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory.
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed),
modify, use or edit our material contact (admin (at) vulnerability-lab (dot) com [email concealed] or research (at) vulnerability-lab (dot) com [email concealed]) to get a permission.