How severe is CVE-2013-7222?

No CVSS score has been assigned to CVE-2013-7222 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-7222?

CVE-2013-7222 affects the following packages: fat_free_crm (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-7222?

Update fat_free_crm to 0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7222 is resolved across your whole dependency graph.

How do I detect CVE-2013-7222 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fat_free_crm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-7222 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-7222 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2013-7222, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-7222?

CVE-2013-7222 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-7222?

CVE-2013-7222 is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-7222 published, and has it been updated?

CVE-2013-7222 was published on May 17, 2022 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

CVE-2013-7222 — fat_free_crm

Fix: fatfreecrm/fat_free_crm@93c182d

CVE-2013-7222 is a CWE-310 vulnerability in fat_free_crm. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for fat_free_crm — see the affected versions and patch details below.

Fat Free CRM has fixed token value

Published

May 17, 2022

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

💎fat_free_crm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

config/initializers/secret_token.rb in Fat Free CRM before 0.12.1 has a fixed FatFreeCRM::Application.config.secret_token value, which makes it easier for remote attackers to spoof signed cookies by referring to the key in the source code.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`fat_free_crm`	all versions	0.12.1`bundle update fat_free_crm --conservative`

Affected Products

1 product · 10 configurations

Application

fat free crmfatfreecrm

≤ 0.12.0

9 versions

0.9.60.9.70.9.80.9.90.9.100.10.10.11.00.11.10.11.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

config/initializers/secret_token.rb in Fat Free CRM before 0.12.1 has a …

phenoelit.orgNVDJan 2014

Report on github.com

github.comNVDJan 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fat_free_crm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fat_free_crm to 0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7222 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

`config/initializers/secret_token.rb` in Fat Free CRM before 0.12.1 has a fixed `FatFreeCRM::Application.config.secret_token` value, which makes it easier for remote attackers to spoof signed cookies by referring to the key in the source code.