CVE-2019-14546 json
An issue was discovered in EspoCRM before 5.6.9.
published 7y ago modified 4mo ago also EUVD-2019-5707
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
An issue was discovered in EspoCRM before 5.6.9. Stored XSS was executed on the Preference page as well as while sending an email when a malicious payload was inserted inside the Email Signature in the Preference page. The attacker could insert malicious JavaScript inside his email signature, which fires when the victim replies or forwards the mail, thus helping him steal victims' cookies (hence compromising their accounts).
Patch / fix
- espocrm espocrm 5.6.9
Is CVE-2019-14546 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gauravnarwani.com https://gauravnarwani.com/publications/CVE-2019-14546/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/espocrm/espocrm/commit/ffd3f762ce4a8de3b8962f33513e073c55d943b5
patch, third-party-advisory
-
gauravnarwani.com
/publications/CVE-2019-14546/
exploit, third-party-advisory
-
github.com
/espocrm/espocrm/releases/tag/5.6.9
release-notes, third-party-advisory
-
github.com
/espocrm/espocrm/issues/1369
third-party-advisory
Sources
- CVE List CVE-2019-14546
- NVD CVE-2019-14546
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.