This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Joyplus-cms
joyplus-cms 1.6.0 has XSS via the manager/collect/collect_vod_zhuiju.php keyword parameter. (2018-07-22, CVE-2018-14500)
joyplus-cms 1.6.0 has XSS via the manager/admin_ajax.php can_search_device array parameter. (2018-07-18, CVE-2018-14388)
joyplus-cms 1.6.0 has XSS in admin_player.php, related to manager/index.php "system manage" and "add" actions. (2018-06-27, CVE-2018-12905)
joyplus-cms 1.6.0 has XSS via the device_name parameter in a manager/admin_ajax.php?action=save flag=add request. (2018-04-13, CVE-2018-10096)
joyplus-cms 1.6.0 has XSS in manager/admin_vod.php via the keyword parameter. (2018-04-12, CVE-2018-10073)
joyplus-cms 1.6.0 has XSS in manager/admin_ajax.php?action=save&tab={pre}vod_type via the t_name parameter. (2018-03-18, CVE-2018-8767)
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>