How severe is CVE-2006-6218?

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

Is CVE-2006-6218 being actively exploited?

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

What products are affected by CVE-2006-6218?

CVE-2006-6218 affects Dev4u Dev4u Cms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2006-6218?

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

CVE-2006-6218 was published on 2006-12-01 and last updated on 2026-06-16.

CVE-2006-6218

CVE-2006-6218 is a high-severity vulnerability in Dev4u Dev4u Cms 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% (64th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Dev4u Dev4u Cms
Published: 2006-12-01
Last modified: 2026-06-16

Description

Multiple SQL injection vulnerabilities in index.php in dev4u CMS allow remote attackers to execute arbitrary SQL commands via the (1) seite_id, (2) gruppe_id.php, and (3) go_target parameters.

Frequently asked questions

What is CVE-2006-6218?: Multiple SQL injection vulnerabilities in index.php in dev4u CMS allow remote attackers to execute arbitrary SQL commands via the (1) seite_id, (2) gruppe_id.php, and (3) go_target parameters.
How severe is CVE-2006-6218?: CVE-2006-6218 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-6218 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-6218?: CVE-2006-6218 affects Dev4u Dev4u Cms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2006-6218?: 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-6218 published?: CVE-2006-6218 was published on 2006-12-01 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:dev4u:dev4u_cms:*:*:*:*:*:*:*:*

More vulnerabilities in Dev4u Dev4u Cms

CVE-2010-0951 — High (CVSS 7.5): SQL injection vulnerability in go_target.php in dev4u CMS allows remote attackers to execute arbitrary SQL commands via…
CVE-2006-6219 — Medium (CVSS 6.8): Multiple cross-site scripting (XSS) vulnerabilities in index.php in dev4u CMS allow remote attackers to inject…

All CVEs affecting Dev4u Dev4u Cms →