Vulnerabilities > Yzmcms > Low
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-09-23 | CVE-2020-19950 | Cross-site Scripting vulnerability in Yzmcms 5.3 A cross-site scripting (XSS) vulnerability in the /banner/add.html component of YzmCMS v5.3 allows attackers to execute arbitrary web scripts or HTML. | 3.5 |
| 2021-09-23 | CVE-2020-19949 | Cross-site Scripting vulnerability in Yzmcms 5.3 A cross-site scripting (XSS) vulnerability in the /link/add.html component of YzmCMS v5.3 allows attackers to execute arbitrary web scripts or HTML. | 3.5 |
| 2021-07-30 | CVE-2020-19118 | Cross-site Scripting vulnerability in Yzmcms 5.2 Cross Site Scripting (XSS) vulnerabiity in YzmCMS 5.2 via the site_code parameter in admin/index/init.html. | 3.5 |
| 2021-06-03 | CVE-2020-35971 | Cross-site Scripting vulnerability in Yzmcms 5.8 A storage XSS vulnerability is found in YzmCMS v5.8, which can be used by attackers to inject JS code and attack malicious XSS on the /admin/system_manage/user_config_edit.html page. | 3.5 |
| 2021-05-10 | CVE-2020-23370 | Cross-site Scripting vulnerability in Yzmcms 5.6 In YzmCMS 5.6, stored XSS exists via the common/static/plugin/ueditor/1.4.3.3/php/controller.php action parameter, which allows remote attackers to upload a swf file. | 3.5 |
| 2019-06-20 | CVE-2018-16247 | Cross-site Scripting vulnerability in Yzmcms 5.1 YzmCMS 5.1 has XSS via the admin/system_manage/user_config_add.html title parameter. | 3.5 |
| 2019-03-11 | CVE-2019-9660 | Cross-site Scripting vulnerability in Yzmcms 5.2 Stored XSS exists in YzmCMS 5.2 via the admin/category/edit.html "catname" parameter. | 3.5 |
| 2019-03-11 | CVE-2019-9661 | Cross-site Scripting vulnerability in Yzmcms 5.2 Stored XSS exists in YzmCMS 5.2 via the admin/system_manage/user_config_edit.html "value" parameter, | 3.5 |
| 2019-03-05 | CVE-2019-9570 | Cross-site Scripting vulnerability in Yzmcms 5.2.0 An issue was discovered in YzmCMS 5.2.0. | 3.5 |
| 2018-12-04 | CVE-2018-19849 | Cross-site Scripting vulnerability in Yzmcms 5.2 An issue was discovered in YzmCMS 5.2. | 3.5 |