This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Yunucms
Cross Site Scripting (XSS) vulnerability exists in YUNUCMS 1.1.9 via the param parameter in the insertContent function in ContentModel.php. (2021-08-12, CVE-2020-18446)
Cross Site Scripting (XSS) vulnerability exists in YUNUCMS 1.1.9 via the upurl function in Page.php. (2021-08-12, CVE-2020-18445)
An issue was discovered in YUNUCMS V1.1.8. app/index/controller/Show.php has an XSS vulnerability via the index.php/index/show/index cw parameter. (2019-01-04, CVE-2019-5311)
YUNUCMS 1.1.8 has XSS in app/admin/controller/System.php because crafted data can be written to the sys.php file, as demonstrated by site_title in an admin/system/basic POST request. (2019-01-04, CVE-2019-5310)
An XSS issue was discovered in admin/banner/editbanner?id=20 in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18725)
An XSS issue was discovered in admin/content/editcontent?id=29&gopage=1 in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18722)
An XSS issue was discovered in admin/link/editlink?id=5 in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18721)
An XSS issue was discovered in admin/sitelink/editsitelink?id=16 in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18726)
An XSS issue was discovered in index.php/admin/area/editarea/id/110000 in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18723)
An XSS issue was discovered in index.php/admin/category/editcategory?id=73 in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18724)
An XSS issue was discovered in index.php/admin/system/basic in YUNUCMS 1.1.5. (2018-10-29, CVE-2018-18720)
Cross-site scripting (XSS) vulnerability in index.php/index/category/index in YUNUCMS 1.1.4 allows remote attackers to inject arbitrary web script or HTML via the area parameter. (2018-09-22, CVE-2018-17322)
YUNUCMS 1.0.7 has XSS via the content title on an admin/content/addcontent/cid/## page (aka a news center page). (2018-04-10, CVE-2018-9993)
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>