# CVE-2013-2118: Privilege escalation in n/a

> Remote attackers can gain editorial privileges in SPIP CMS via a vulnerability in the filtering script, allowing unauthorized content control.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 9 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2013-2118, DSA-2694-1, GHSA-rvp2-88r9-jj4j

## What is CVE-2013-2118?

CVE-2013-2118 is a high-severity vulnerability in Spip Spip, published on 9 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SPIP 3.0.x before 3.0.9, 2.1.x before 2.1.22, and 2.0.x before 2.0.23 allows remote attackers to gain privileges and "take editorial control" via vectors related to ecrire/inc/filtres.php.

## Which versions are affected by CVE-2013-2118?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2013-2118?

Upgrade to a fixed version.

## Is CVE-2013-2118 being exploited?

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

Public exploit code:

- SPIP CMS < 2.0.23/ 2.1.22/3.0.9 - Privilege Escalation (exploitdb)

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

What it is: CVE-2013-2118 is a high-severity vulnerability in Spip Spip, published on 9 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2118 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-2013-2118/ (Markdown: https://insights.sbomify.com/CVE-2013-2118/index.md)
```

## Sources

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

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