# CVE-2016-3154: Deserialization in n/a

> Remote attackers can execute arbitrary PHP code in SPIP CMS via crafted serialized objects in the encoder_contexte_ajax function.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-3154, GHSA-5fwq-26jx-xp73, UBUNTU-CVE-2016-3154

## What is CVE-2016-3154?

CVE-2016-3154 is a critical unsafe deserialization vulnerability in Spip Spip, published on 8 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The encoder_contexte_ajax function in ecrire/inc/filtres.php in SPIP 2.x before 2.1.19, 3.0.x before 3.0.22, and 3.1.x before 3.1.1 allows remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via a crafted serialized object.

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

## Which versions are affected by CVE-2016-3154?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2016-3154?

Upgrade to a fixed version.

## Is CVE-2016-3154 being exploited?

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

## 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-2016-3154 and fix it if it is affected.

What it is: CVE-2016-3154 is a critical unsafe deserialization vulnerability in Spip Spip, published on 8 Apr 2016. 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-2016-3154 in the wild and no public exploit code.

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

## Sources

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

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