CVE-2013-7224 json
Fat Free CRM allows remote attackers to obtain sensitive information via a direct request
published 12y ago modified 4mo ago also GHSA-4xq9-vw89-p5cx , EUVD-2022-2472
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Fat Free CRM before 0.12.1 does not restrict JSON serialization, which allows remote attackers to obtain sensitive information via a direct request, as demonstrated by a request for users/1.json.
Patch / fix
Is CVE-2013-7224 in your dependencies? 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
2.53% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- 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
-
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-7224
advisory
-
github.com
/fatfreecrm/fat_free_crm
package
Sources
- CVE List CVE-2013-7224
- GitHub Advisory GHSA-4xq9-vw89-p5cx
- NVD CVE-2013-7224
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.