CVE-2008-5812: 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…
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.1% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: spip (Debian:13) 2.0.6-1.
Add it to your regular patch cycle. Upgrade to spip (Debian:13) 2.0.6-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 2, 2009
- Updated
- Jun 16, 2026
- EPSS
- 1.5% · 75th percentile
- CWE
- —
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| spip | spip | cpe:2.3:a:spip:spip |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- spip spip1.8
- spip spip1.8.1
- spip spip1.8.2
- spip spip1.8.2b
- spip spip1.8.3
- spip spip1.8b1
- spip spip1.8b2
- spip spip1.8b3
+9 more rows
- spip spip1.8b4
- spip spip1.8b5
- spip spip1.8b6
- spip spip1.9.0
- spip spip1.9.1
- spip spip1.9.2
- spip spip1.9.2f
- spip spip2.0.0
- spip spip2.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | spip | before 2.0.6-1 | 2.0.6-1 |
Same product
spip: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-27372SPIP before 4.2.1 allows Remote Code Execution via form values in the public area because serialization is mishandled.69This week
- CVE-2024-8517SPIP Bigup Multipart File Upload OS Command Injection67This week
- CVE-2024-7954SPIP porte_plume Plugin Arbitrary PHP Execution66This week
Published before and after this one in the same product
- ← EarlierCVE-2006-1702Apr 11, 2006 · PHP remote file inclusion vulnerability in spip_login.php3 in SPIP 1.8.3 allows remote attackers to execute arbitrary PHP code via a URL in…31Monitor
- ← EarlierCVE-2007-4525Aug 24, 2007 · PHP remote file inclusion vulnerability in inc-calcul.php3 in SPIP 1.7.2 allows remote attackers to execute arbitrary PHP code via a URL in…30Monitor
- Later →CVE-2008-5813Jan 2, 2009 · SQL injection vulnerability in inc/rubriques.php in SPIP 1.8 before 1.8.3b, 1.9 before 1.9.2g, and 2.0 before 2.0.2 allows remote attackers…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:spip | 2.0.6-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.