Search
Search Results (49 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2019-14351 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| EspoCRM 5.6.4 is vulnerable to user password hash enumeration. A malicious authenticated attacker can brute-force a user password hash by 1 symbol at a time using specially crafted api/v1/User?filterList filters. | ||||
| CVE-2019-14350 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| EspoCRM 5.6.4 is vulnerable to stored XSS due to lack of filtration of user-supplied data in the Knowledge base. A malicious attacker can inject JavaScript code in the body parameter during api/v1/KnowledgeBaseArticle knowledge-base record creation. | ||||
| CVE-2019-14349 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| EspoCRM version 5.6.4 is vulnerable to stored XSS due to lack of filtration of user-supplied data in the api/v1/Document functionality for storing documents in the account tab. An attacker can upload a crafted file that contains JavaScript code in its name. This code will be executed when a user opens a page of any profile with this. | ||||
| CVE-2019-14331 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| An issue was discovered in EspoCRM before 5.6.6. Stored XSS exists due to lack of filtration of user-supplied data in Create User. A malicious attacker can modify the firstName and lastName to contain JavaScript code. | ||||
| CVE-2019-14330 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| An issue was discovered in EspoCRM before 5.6.6. Stored XSS exists due to lack of filtration of user-supplied data in Create Case. A malicious attacker can modify the firstName and lastName to contain JavaScript code. | ||||
| CVE-2019-14329 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| An issue was discovered in EspoCRM before 5.6.6. There is stored XSS due to lack of filtration of user-supplied data in Create Task. A malicious attacker can modify the parameter name to contain JavaScript code. | ||||
| CVE-2019-13643 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| Stored XSS in EspoCRM before 5.6.4 allows remote attackers to execute malicious JavaScript and inject arbitrary source code into the target pages. The attack begins by storing a new stream message containing an XSS payload. The stored payload can then be triggered by clicking a malicious link on the Notifications page. | ||||
| CVE-2018-17302 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| Stored XSS exists in views/fields/wysiwyg.js in EspoCRM 5.3.6 via a /#Email/view saved draft message. | ||||
| CVE-2018-17301 | 1 Espocrm | 1 Espocrm | 2024-11-21 | N/A |
| Reflected XSS exists in client/res/templates/global-search/name-field.tpl in EspoCRM 5.3.6 via /#Account in the search panel. | ||||