# CVE-2022-37155: Code injection in n/a

> Remote authenticated users can execute arbitrary code in SPIP CMS via the _oups parameter, requiring immediate patching.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-37155, DSA-5190-1, GHSA-7c7w-25xj-4mp8, UBUNTU-CVE-2022-37155

## What is CVE-2022-37155?

CVE-2022-37155 is a high-severity code injection vulnerability in Spip Spip, published on 13 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RCE in SPIP 3.1.13 through 4.1.2 allows remote authenticated users to execute arbitrary code via the _oups parameter.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-37155?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2022-37155?

Apply the vendor's patch.

## Is CVE-2022-37155 being exploited?

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

## Other vulnerabilities in Spip Spip

- [CVE-2012-4331](https://insights.sbomify.com/CVE-2012-4331/): Other in n/a (critical 10.0)
- [CVE-2008-5812](https://insights.sbomify.com/CVE-2008-5812/): Other in n/a (critical 10.0)
- [CVE-2024-8517](https://insights.sbomify.com/CVE-2024-8517/): SPIP Bigup Multipart File Upload OS Command Injection (critical 9.8)
- [CVE-2023-24258](https://insights.sbomify.com/CVE-2023-24258/): SQL injection in n/a (critical 9.8)
- [CVE-2017-9736](https://insights.sbomify.com/CVE-2017-9736/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37155 and fix it if it is affected.

What it is: CVE-2022-37155 is a high-severity code injection vulnerability in Spip Spip, published on 13 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-37155 exists.

Affected product: Spip Spip. 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-2022-37155/ (Markdown: https://insights.sbomify.com/CVE-2022-37155/index.md)
```

## Sources

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

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