This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Metinfo
MetInfo 7.0 beta contains a stored cross-site scripting (XSS) vulnerability in the $name parameter of admin/?n=column&c=index&a=doAddColumn. (2021-12-22, CVE-2020-20600)
Cross Site Scripting (XSS) vulnerability in MetInfo 7.0.0 via the gourl parameter in login.php. (2021-06-21, CVE-2020-21517)
MetInfo 6.x through 6.1.3 has XSS via the /admin/login/login_check.php url_array[] parameter. (2018-12-26, CVE-2018-20486)
In Metinfo 6.1.3, include/interface/applogin.php allows setting arbitrary HTTP headers (including the Cookie header), and common.inc.php allows registering variables from the $_COOKIE value. This issue can, for example, be exploited in conjunction with CVE-2018-19835 to bypass many XSS filters such as the Chrome XSS filter. (2018-12-03, CVE-2018-19836)
Metinfo 6.1.3 has reflected XSS via the admin/column/move.php lang_columnerr4 parameter. (2018-12-03, CVE-2018-19835)
MetInfo 6.1.3 has XSS via the admin/index.php?a=dogetpassword abt_type parameter. (2018-11-07, CVE-2018-19051)
MetInfo 6.1.3 has XSS via the admin/index.php?a=dogetpassword langset parameter. (2018-11-07, CVE-2018-19050)
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter. (2018-10-16, CVE-2018-18374)
MetInfo 6.1.2 has XSS via the /admin/index.php bigclass parameter in an n=column&a=doadd action. (2018-10-15, CVE-2018-18296)
MetInfo 6.0.0 allows XSS via a modified name of the navigation bar on the home page. (2018-07-20, CVE-2018-14419)
The front page of MetInfo 6.0 allows XSS by sending a feedback message to an administrator. (2018-04-10, CVE-2018-9985)
Cross-site scripting (XSS) vulnerability in save.php in MetInfo 6.0 allows remote attackers to inject arbitrary web script or HTML via the webname or weburl parameter. (2018-04-10, CVE-2018-9928)
Cross Site Scripting (XSS) exists in MetInfo 6.0.0 via /feedback/index.php because app/system/feedback/web/feedback.class.php mishandles input data. (2018-03-07, CVE-2018-7721)
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>