How severe is CVE-2006-0626?

CVE-2006-0626 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2006-0626 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-0626?

CVE-2006-0626 affects Spip. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2006-0626?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2006-0626 published?

CVE-2006-0626 was published on 2006-02-09 and last updated on 2026-06-16.

CVE-2006-0626

CVE-2006-0626 is a high-severity vulnerability in Spip with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Spip
Published: 2006-02-09
Last modified: 2026-06-16

Description

SQL injection vulnerability in spip_acces_doc.php3 in SPIP 1.8.2g and earlier allows remote attackers to execute arbitrary SQL commands via the file parameter.

Frequently asked questions

What is CVE-2006-0626?: SQL injection vulnerability in spip_acces_doc.php3 in SPIP 1.8.2g and earlier allows remote attackers to execute arbitrary SQL commands via the file parameter.
How severe is CVE-2006-0626?: CVE-2006-0626 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-0626 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-0626?: CVE-2006-0626 affects Spip. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2006-0626?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2006-0626 published?: CVE-2006-0626 was published on 2006-02-09 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:spip:spip:1.8.2g:*:*:*:*:*:*:*

More vulnerabilities in Spip

CVE-2012-4331 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in SPIP before 1.9.2.o, 2.0.x before 2.0.18, and 2.1.x before 2.1.13 have unknown…
CVE-2008-5812 — Critical (CVSS 10.0): 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…
CVE-2024-8517 — Critical (CVSS 9.8): SPIP before 4.3.2, 4.2.16, and 4.1.18 is vulnerable to a command injection issue. A remote and unauthenticated…
CVE-2023-27372 — Critical (CVSS 9.8): SPIP before 4.2.1 allows Remote Code Execution via form values in the public area because serialization is mishandled.…
CVE-2023-24258 — Critical (CVSS 9.8): SPIP v4.1.5 and earlier was discovered to contain a SQL injection vulnerability via the _oups parameter. This…
CVE-2020-28984 — Critical (CVSS 9.8): prive/formulaires/configurer_preferences.php in SPIP before 3.2.8 does not properly validate the couleur, display,…

All CVEs affecting Spip →