How severe is CVE-2006-4202?

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

Is CVE-2006-4202 being actively exploited?

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

What products are affected by CVE-2006-4202?

CVE-2006-4202 affects Spidey Blog Spidey Blog Script. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2006-4202?

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-4202 published?

CVE-2006-4202 was published on 2006-08-17 and last updated on 2026-06-16.

CVE-2006-4202

CVE-2006-4202 is a high-severity vulnerability in Spidey Blog Spidey Blog Script 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% (66th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Spidey Blog Spidey Blog Script
Published: 2006-08-17
Last modified: 2026-06-16

Description

SQL injection vulnerability in proje_goster.php in Spidey Blog Script 1.5 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter.

Frequently asked questions

What is CVE-2006-4202?: SQL injection vulnerability in proje_goster.php in Spidey Blog Script 1.5 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter.
How severe is CVE-2006-4202?: CVE-2006-4202 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-4202 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-4202?: CVE-2006-4202 affects Spidey Blog Spidey Blog Script. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2006-4202?: 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-4202 published?: CVE-2006-4202 was published on 2006-08-17 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:spidey_blog:spidey_blog_script:*:*:*:*:*:*:*:*