CVE-2019-10226 json
Withdrawn Advisory: Fat Free CRM Cross-site Scripting vulnerability
published 2019-06-10 7 y ago modified 2026-09-10 1 mo ago also GHSA-gmg5-r3c4-3fm9 , EUVD-2022-3978
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
HTML Injection has been discovered in the v0.19.0 version of the Fat Free CRM product via an authenticated request to the /comments URI. NOTE: the vendor disputes the significance of this report because some HTML formatting (such as with an H1 element) is allowed, but there is a XSS protection mechanism.
Timeline
- First public exploit (EDB-46617)
- Published
Exploit prediction
4.70% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-46617 Fat Free CRM 0.19.0 - HTML Injection webapps, 2019-03-28
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
exploit-db.com
/exploits/46617/
exploit
-
packetstormsecurity.com
/files/152263/Fat-Free-CRM-0.19.0-HTML-Injection.html
web, third-party-advisory, vdb-entry
-
github.com
/fatfreecrm/fat_free_crm/issues/1235
web
-
github.com
/fatfreecrm/fat_free_crm/blob/master/app/views/comments/_comment.html.haml#L2
web
-
apidock.com
/rails/ActionView/Helpers/TextHelper/simple_format
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-10226
advisory
-
github.com
/github/advisory-database/pull/3599
web
-
github.com
/fatfreecrm/fat_free_crm
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/fat_free_crm/CVE-2019-10226.yml
web
-
exploit-db.com
/exploits/46617
web
Sources
- CVE List CVE-2019-10226
- GitHub Advisory GHSA-gmg5-r3c4-3fm9
- NVD CVE-2019-10226
Fencer Vulns 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.