# CVE-2026-130869: Ruby Central cfp-app through 2.0 Missing Authorization in CommentsController#create


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-rwg8-28hv-mwx6

## What is CVE-2026-130869?

CVE-2026-130869 is a medium-severity vulnerability in Ruby Central cfp-app, published on 17 Nov 2026. 

### Official description

Ruby Central cfp-app through 2.0 contains a missing authorization vulnerability in CommentsController#create that allows any authenticated user to comment on any proposal by supplying a numeric proposal_id. Attackers can send POST requests to /public_comments or /internal_comments to post into reviewers' private discussions and trigger notifications to event team members.

Weakness: CWE-862 (Missing Authorization)

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

1 open source package ship an affected version, including rubycentral/cfp-app.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `rubycentral/cfp-app` | GitHub | `pkg:github/rubycentral/cfp-app` | All versions to 2.0 | None |

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

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

## Is CVE-2026-130869 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130869 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130869 is a medium-severity vulnerability in Ruby Central cfp-app, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130869 exists.

Affected packages and fixed versions:
- rubycentral/cfp-app (GitHub): affected all versions up to 2.0; no fix listed

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-130869/ (Markdown: https://insights.sbomify.com/CVE-2026-130869/index.md)
```

## Sources

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

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