Vulnerabilities > Intelliants > Subrion
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2020-05-15 | CVE-2019-20389 | Cross-site Scripting vulnerability in Intelliants Subrion 4.2.1 An XSS issue was identified on the Subrion CMS 4.2.1 /panel/configuration/general settings page. | 6.1 |
2020-04-29 | CVE-2020-12469 | Deserialization of Untrusted Data vulnerability in Intelliants Subrion admin/blocks.php in Subrion CMS through 4.2.1 allows PHP Object Injection (with resultant file deletion) via serialized data in the subpages value within a block to blocks/edit. | 6.5 |
2020-04-29 | CVE-2020-12468 | Unspecified vulnerability in Intelliants Subrion 4.2.1 Subrion CMS 4.2.1 allows CSV injection via a phrase value within a language. | 7.8 |
2020-04-29 | CVE-2020-12467 | Session Fixation vulnerability in Intelliants Subrion 4.2.1 Subrion CMS 4.2.1 allows session fixation via an alphanumeric value in a session cookie. | 6.5 |
2020-03-17 | CVE-2018-21037 | Cross-Site Request Forgery (CSRF) vulnerability in Intelliants Subrion Subrion CMS 4.1.5 (and possibly earlier versions) allow CSRF to change the administrator password via the panel/members/edit/1 URI. | 8.8 |
2019-10-06 | CVE-2019-17225 | Cross-site Scripting vulnerability in Intelliants Subrion 4.2.1 Subrion 4.2.1 allows XSS via the panel/members/ Username, Full Name, or Email field, aka an "Admin Member JSON Update" issue. | 5.4 |
2019-07-03 | CVE-2018-11317 | Cross-site Scripting vulnerability in Intelliants Subrion Subrion CMS before 4.1.4 has XSS. | 6.1 |
2018-10-02 | CVE-2018-15563 | Cross-site Scripting vulnerability in Intelliants Subrion 4.2.1 _core/admin/pages/add/ in Subrion CMS 4.2.1 has XSS via the titles[en] parameter. | 6.1 |
2018-09-01 | CVE-2018-16327 | Cross-site Scripting vulnerability in Intelliants Subrion 4.2.1 There is Stored XSS in Subrion 4.2.1 via the admin panel URL configuration. | 4.8 |
2018-08-02 | CVE-2018-14840 | Cross-site Scripting vulnerability in Intelliants Subrion 4.2.1 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). | 6.1 |