This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Subrion
A cross-site scripting (XSS) vulnerability exists in the "contact us" plugin for Subrion CMS <= 4.2.1 version via "List of subjects". (2022-04-29, CVE-2021-41948)
Cross-Site Scripting (XSS) vulnerability in Subrion 4.2.1 via the title when adding a page. (2021-08-06, CVE-2020-22330)
Cross Site Scripting (XSS) vulnerability in subrion CMS Version <= 4.2.1 allows remote attackers to execute arbitrary web script via the "payment gateway" column on transactions tab. (2021-04-09, CVE-2020-23761)
Subrion CMS v4.2.1 allows XSS via the panel/phrases/ VALUE parameter. (2020-11-04, CVE-2019-7356)
An XSS issue was identified on the Subrion CMS 4.2.1 /panel/configuration/general settings page. A remote attacker can inject arbitrary JavaScript code in the v[language_switch] parameter (within multipart/form-data), which is reflected back within a user's browser without proper output encoding. (2020-05-15, CVE-2019-20389)
Subrion 4.2.1 allows XSS via the panel/members/ Username, Full Name, or Email field, aka an "Admin Member JSON Update" issue. (2019-10-06, CVE-2019-17225)
Subrion CMS before 4.1.4 has XSS. (2019-07-03, CVE-2018-11317)
_core/admin/pages/add/ in Subrion CMS 4.2.1 has XSS via the titles[en] parameter. (2018-10-02, CVE-2018-15563)
There is Stored XSS in Subrion 4.2.1 via the admin panel URL configuration. (2018-09-01, CVE-2018-16327)
uploads/.htaccess in Subrion CMS 4.2.1 allows XSS because it does not block .html file uploads (but does block, for example, .htm file uploads). (2018-08-02, CVE-2018-14840)
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>