This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Zzcms
An issue was discovered in ZZCMS 2022. There is a cross-site scripting (XSS) vulnerability in admin/ad_list.php. (2022-12-07, CVE-2022-44361)
An issue was discovered in ZZCMS 2021. There is a cross-site scripting (XSS) vulnerability in ad_manage.php. (2022-04-08, CVE-2021-46437)
Cross Site Scripting (XSS) vulnerability exists in zzcms 2019 XSS via a modify action in user/adv.php. (2021-12-13, CVE-2020-19042)
An issue was discovered in zzcms2020. There is a XSS vulnerability that can insert and execute JS code arbitrarily via /user/manage.php. (2021-06-03, CVE-2020-35973)
There is a XSS in the user login page in zzcms 2019. Users can inject js code by the referer header via user/login.php (2020-12-18, CVE-2020-20285)
XSS exists in zzcms v8.3 via the /uploadimg_form.php noshuiyin parameter. (2019-03-07, CVE-2018-17413)
zzcms 2019 has XSS via an arbitrary user/ask.php?do=modify parameter because inc/stopsqlin.php does not block a mixed-case string such as sCrIpT. (2019-02-24, CVE-2019-9078)
zzcms 8.3 has stored XSS related to the content variable in user/manage.php and zt/show.php. (2018-08-06, CVE-2018-14962)
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>