# CVE-2025-47292: Cap Collectif vulnerable to insecure deserialization leading to remote code execution

> Unauthenticated attackers can achieve remote code execution via insecure deserialization in the DebateAlternateArgumentsResolver component.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2025
- **Updated:** 14 May 2025
- **Also known as:** GHSA-hf7r-rjh4-5fc8

## What is CVE-2025-47292?

CVE-2025-47292 is a critical unsafe deserialization vulnerability in cap-collectif, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cap Collectif is an online decision making platform that integrates several tools. Before commit 812f2a7d271b76deab1175bdaf2be0b8102dd198, the `DebateAlternateArgumentsResolver` deserializes a `Cursor`, allowing any classes and which can be controlled by unauthenticated user. Exploitation of this vulnerability can lead to Remote Code Execution. The vulnerability is fixed in commit 812f2a7d271b76deab1175bdaf2be0b8102dd198.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-47292?


## How do I fix CVE-2025-47292?

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

## Is CVE-2025-47292 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47292 and fix it if it is affected.

What it is: CVE-2025-47292 is a critical unsafe deserialization vulnerability in cap-collectif, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47292 in the wild and no public exploit code.

Affected product: cap-collectif. 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-2025-47292/ (Markdown: https://insights.sbomify.com/CVE-2025-47292/index.md)
```

## Sources

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

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