This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Seacms
Cross Site Scripting (XSS) vulnerability exists in SeaCMS 12.6 via the (1) v_company and (2) v_tvs parameters in /admin_video.php, (2021-08-17, CVE-2021-29313)
A cross-site scripting (XSS) vulnerability has been discovered in the login page of SeaCMS version 11 which allows an attacker to inject arbitrary web script or HTML. (2021-05-28, CVE-2020-26642)
In SeaCMS v6.6.4, there is stored XSS via the member.php?action=chgpwdsubmit email parameter during a password change, as demonstrated by a data: URL in an OBJECT element. (2018-11-17, CVE-2018-19350)
An issue was discovered in SeaCMS 6.64. XSS exists in admin_datarelate.php via the time or maxHit parameter in a dorandomset action. (2018-09-22, CVE-2018-17321)
An issue was discovered in SeaCMS 6.64. XSS exists in admin_video.php via the action, area, type, yuyan, jqtype, v_isunion, v_recycled, v_ismoney, or v_ispsd parameter. (2018-09-16, CVE-2018-17062)
SeaCMS V6.61 has XSS via the admin_video.php v_content parameter, related to the site name. (2018-09-02, CVE-2018-16348)
SeaCMS 6.61 has two XSS issues in the admin_config.php file via certain form fields. (2018-07-23, CVE-2018-14517)
SeaCMS V6.61 has XSS via the site name parameter on an adm1n/admin_config.php page (aka a system management page). (2018-06-14, CVE-2018-12431)
SeaCMS 6.61 has stored XSS in admin_collect.php via the siteurl parameter. (2018-05-31, CVE-2018-11583)
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>