This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Wtcms
WTCMS 1.0 contains a reflective cross-site scripting (XSS) vulnerability in the keyword search function under the background articles module. (2021-09-01, CVE-2020-20344)
WTCMS 1.0 contains a reflective cross-site scripting (XSS) vulnerability in the page management background which allows attackers to obtain cookies via a crafted payload entered into the search box. (2021-09-01, CVE-2020-20345)
WTCMS 1.0 contains a stored cross-site scripting (XSS) vulnerability in the link address field under the background links module. (2021-09-01, CVE-2020-20349)
WTCMS 1.0 contains a stored cross-site scripting (XSS) vulnerability in the link field under the background menu management module. (2021-09-01, CVE-2020-20348)
WTCMS 1.0 contains a stored cross-site scripting (XSS) vulnerability in the source field under the article management module. (2021-09-01, CVE-2020-20347)
WTCMS 1.0 allows index.php?g=admin&m=index&a=index CSRF with resultant XSS. (2019-09-23, CVE-2019-16719)
An issue was discovered in WTCMS 1.0. It has stored XSS via the third text box (for the website statistics code). (2019-02-18, CVE-2019-8911)
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>