CVE-2019-14331
UnknownEPSS 1.33%
Last modified
CVE-2019-14331 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.33% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Espocrm | Espocrm | < 5.6.6 |
References
- http://www.cinquino.eu/EspoCRM.htmExploit, Third Party Advisory
- https://github.com/espocrm/espocrm/commit/4ab7d19776011288b875abd3eef1e1f6f75289e2Patch, Third Party Advisory
- https://github.com/espocrm/espocrm/compare/5.6.5...5.6.6Third Party Advisory
- http://www.cinquino.eu/EspoCRM.htmExploit, Third Party Advisory
- https://github.com/espocrm/espocrm/commit/4ab7d19776011288b875abd3eef1e1f6f75289e2Patch, Third Party Advisory
- https://github.com/espocrm/espocrm/compare/5.6.5...5.6.6Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-14331?
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.
How severe is CVE-2019-14331?
Severity scoring for CVE-2019-14331 is pending analysis. The EPSS model estimates a 1.33% probability of exploitation in the next 30 days.
How do I fix CVE-2019-14331?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2019-14331?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST