This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Ucms
UCMS v1.6.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the Import function under the Site Management page. (2022-09-19, CVE-2022-38527)
A stored cross-site scripting (XSS) vulnerability in /ucms/index.php?do=list_edit of UCMS 1.4.7 allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the title, key words, description or content text fields. (2021-09-29, CVE-2020-20781)
An issue was discovered in UCMS 1.4.6. There is XSS in the title bar, as demonstrated by a do=list request. (2019-03-07, CVE-2018-16804)
sadmin\cedit.php in UCMS 1.4.7 has XSS via an index.php sadmin_cedit action. (2018-12-30, CVE-2018-20600)
UCMS 1.4.7 has XSS via the description parameter in an index.php list_editpost action. (2018-12-30, CVE-2018-20601)
UCMS 1.4.7 has XSS via the dir parameter in an index.php sadmin_fileedit action. (2018-12-30, CVE-2018-20597)
An issue was discovered in UCMS 1.4.6. aaddpost.php has stored XSS via the sadmin/aindex.php minfo parameter in a sadmin_aaddpost action. (2018-09-21, CVE-2018-17320)
UCMS 1.4.6 has XSS via the install/index.php mysql_dbname parameter. (2018-09-14, CVE-2018-17034)
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>