This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Phpmywind
Cross Site Scripting (XSS) in PHPMyWind v5.5 allows remote attackers to execute arbitrary code by injecting scripts into the parameter "$cfg_copyright" of component " /admin/web_config.php". (2021-05-27, CVE-2020-18229)
Cross Site Scripting (XSS) in PHPMyWind v5.5 allows remote attackers to execute arbitrary code by injecting scripts into the parameter "$cfg_switchshow" of component " /admin/web_config.php". (2021-05-27, CVE-2020-18230)
admin/infoclass_update.php in PHPMyWind 5.6 has stored XSS. (2019-09-23, CVE-2019-16704)
admin/infolist_add.php in PHPMyWind 5.6 has stored XSS. (2019-09-23, CVE-2019-16703)
An issue was discovered in PHPMyWind 5.5. The method parameter of the data/api/oauth/connect.php page has a reflected Cross-site Scripting (XSS) vulnerability. (2019-03-07, CVE-2019-7661)
An issue was discovered in PHPMyWind 5.5. The username parameter of the /install/index.php page has a stored Cross-site Scripting (XSS) vulnerability, as demonstrated by admin/login.php. (2019-03-07, CVE-2019-7660)
admin/default.php in PHPMyWind v5.5 has XSS via an HTTP Host header. (2019-02-18, CVE-2019-8435)
An issue was discovered in PHPMyWind 5.5. The GetQQ function in include/func.class.php allows XSS via the cfg_qqcode parameter. This can be exploited via CSRF. (2019-02-05, CVE-2019-7402)
PHPMyWind 5.5 has XSS in member.php via an HTTP Referer header, (2018-09-17, CVE-2018-17130)
PHPMyWind 5.5 has XSS via the cid parameter to newsshow.php, or the query string to news.php or about.php. (2018-05-26, CVE-2018-11487)
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>