CVE-2013-7223 json
Fat Free CRM contains Cross-site Request Forgery vulnerablilities
published 12y ago modified 4mo ago also GHSA-mcvq-7xjq-46x6 , EUVD-2022-4544
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in Fat Free CRM before 0.12.1 allow remote attackers to hijack the authentication of unspecified victims via unknown vectors, related to the lack of a protect_from_forgery line in app/controllers/application_controller.rb.
Patch / fix
Is CVE-2013-7223 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
1.20% chance of exploitation in the next 30 days, higher than 68% 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 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | fat_free_crm | <0.12.1 |
0.12.1 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/fatfreecrm/fat_free_crm/commit/a7fedbb36388bad0c0f32b2346481e0ea126dea6
web, 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-7223
advisory
-
github.com
/fatfreecrm/fat_free_crm
package
Sources
- CVE List CVE-2013-7223
- GitHub Advisory GHSA-mcvq-7xjq-46x6
- NVD CVE-2013-7223
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.