Fat Free CRM vulnerable to Exposure of Sensitive Information

published 2014-01-02 12 y ago modified 2026-06-17 4 mo ago also GHSA-f25h-3mj6-4jpg , EUVD-2022-3668

cvss: 5.0; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.6%; EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits: 0; none known

Fat Free CRM before 0.12.1 does not restrict XML serialization, which allows remote attackers to obtain sensitive information via a direct request, as demonstrated by a request for users/1.xml, a different vulnerability than CVE-2013-7224.

Patch / fix

fixed in 1 links 1

rubygems fat_free_crm 0.12.1

github.com/fatfreecrm/fat_free_crm@cf26a04 commit

Exploit prediction

2.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/fatfreecrm/fat_free_crm/commit/cf26a04b356ad2161c4c6160260eb870a3de5328 referenced PoC, tagged "exploit" by a source, unverified
phenoelit.org http://www.phenoelit.org/stuff/ffcrm.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
rubygems	fat_free_crm	<0.12.1	0.12.1

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

github.com /fatfreecrm/fat_free_crm/commit/cf26a04b356ad2161c4c6160260eb870a3de5328
web, exploit, patch
phenoelit.org /stuff/ffcrm.txt
exploit
github.com /fatfreecrm/fat_free_crm/wiki/Fixing-security-vulnerabilities-%2827th-Dec-2013%29
web, vendor-advisory
seclists.org /fulldisclosure/2013/Dec/199
mailing-list, web
openwall.com /lists/oss-security/2013/12/28/2
mailing-list, web
github.com /fatfreecrm/fat_free_crm/issues/300
web
nvd.nist.gov /vuln/detail/CVE-2013-7249
advisory
github.com /fatfreecrm/fat_free_crm
package

Sources

CVE List CVE-2013-7249
GitHub Advisory GHSA-f25h-3mj6-4jpg
NVD CVE-2013-7249

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.

Summary