# CVE-2026-113600: Fat Free CRM before 0.26.0 IDOR via CommentsController update and destroy


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-gh75-88g6-gr96

## What is CVE-2026-113600?

CVE-2026-113600 is a medium-severity vulnerability in fatfreecrm fat_free_crm, published on 20 Oct 2026. 

### Official description

Fat Free CRM before 0.26.0 contains an insecure direct object reference vulnerability that allows authenticated users to modify or delete other users' comments because CommentsController#update and #destroy use an unscoped Comment.find without authorization checks. Attackers can send PUT or DELETE requests to /comments/:id with enumerable sequential IDs to edit or delete comments on contacts, accounts, leads, and opportunities owned by others.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-113600?


## How do I fix CVE-2026-113600?

No fix has been published for CVE-2026-113600 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113600 being exploited?

There is no known exploitation of CVE-2026-113600 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113600 and fix it if it is affected.

What it is: CVE-2026-113600 is a medium-severity vulnerability in fatfreecrm fat_free_crm, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113600 in the wild and no public exploit code.

Affected product: fatfreecrm fat_free_crm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113600/ (Markdown: https://insights.sbomify.com/CVE-2026-113600/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113600
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113600
- OSV: https://osv.dev/vulnerability/CVE-2026-113600

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113600/
Summaries are generated and may contain mistakes; the official description above is the record.