This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Hongcms
HongCMS 3.0.0 has XSS via the install/index.php dbname parameter. (2019-10-16, CVE-2019-17608)
HongCMS 3.0.0 has XSS via the install/index.php dbpassword parameter. (2019-10-16, CVE-2019-17610)
HongCMS 3.0.0 has XSS via the install/index.php dbusername parameter. (2019-10-16, CVE-2019-17609)
HongCMS 3.0.0 has XSS via the install/index.php servername parameter. (2019-10-16, CVE-2019-17607)
HongCMS 3.0.0 has XSS via the install/index.php tableprefix parameter. (2019-10-16, CVE-2019-17611)
system\errors\404.php in HongCMS 3.0.0 has XSS via crafted input that triggers a 404 HTTP status code. (2018-06-13, CVE-2018-12266)
An issue was discovered in HongCMS 3.0.0. The post news feature has Stored XSS via the content field. (2018-04-26, CVE-2018-10422)
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>