# CVE-2008-5812: Other in n/a

> Multiple unspecified vulnerabilities in SPIP allow attackers to potentially compromise the system, requiring an upgrade to a patched version.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 2 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5812, GHSA-w3r6-3rf8-9crv

## What is CVE-2008-5812?

CVE-2008-5812 is a critical vulnerability in Spip Spip, published on 2 Jan 2009. 

### Official description

Multiple unspecified vulnerabilities in SPIP 1.8 before 1.8.3b, 1.9 before 1.9.2g, and 2.0 before 2.0.2 have unknown impact and attack vectors.

## Which versions are affected by CVE-2008-5812?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2008-5812?

Upgrade to a fixed version.

## Is CVE-2008-5812 being exploited?

There is no known exploitation of CVE-2008-5812 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-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)
- [CVE-2016-3154](https://insights.sbomify.com/CVE-2016-3154/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5812 and fix it if it is affected.

What it is: CVE-2008-5812 is a critical vulnerability in Spip Spip, published on 2 Jan 2009. 
Exploitation: There is no known exploitation of CVE-2008-5812 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-2008-5812/ (Markdown: https://insights.sbomify.com/CVE-2008-5812/index.md)
```

## Sources

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

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