CVE-2015-1585 json
Fat Free CRM Cross-Site Request Forgery vulnerability
published 2015-02-19 11 y ago modified 2026-06-17 4 mo ago also GHSA-wx7c-8j35-mpg8 , EUVD-2022-5667
- cvss
- 6.8
- version 2.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
Fat Free CRM before 0.13.6 allows remote attackers to conduct cross-site request forgery (CSRF) attacks via a request without the authenticity_token, as demonstrated by a crafted HTML page that creates a new administrator account.
Patch / fix
Exploit 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
- packetstormsecurity.com http://packetstormsecurity.com/files/130410/Fat-Free-CRM-0.13.5-Cross-Site-Request-Forgery.html 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.13.6 |
0.13.6 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/fatfreecrm/fat_free_crm/commit/86fd7f98c9583fd36384987282d1c086fdcecd7c
web
-
packetstormsecurity.com
/files/130410/Fat-Free-CRM-0.13.5-Cross-Site-Request-Forgery.html
web, exploit
-
github.com
/fatfreecrm/fat_free_crm/wiki/CSRF-Vulnerability-%28CVE-2015-1585%29
web
-
securityfocus.com
/archive/1/534709/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/100925
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2015-1585
advisory
-
github.com
/fatfreecrm/fat_free_crm
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/fat_free_crm/CVE-2015-1585.yml
web
Sources
- CVE List CVE-2015-1585
- GitHub Advisory GHSA-wx7c-8j35-mpg8
- NVD CVE-2015-1585
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.