How severe is CVE-2006-1123?

CVE-2006-1123 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2006-1123 being actively exploited?

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

What products are affected by CVE-2006-1123?

CVE-2006-1123 primarily affects D2ksoft D2kblog. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-1123?

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

When was CVE-2006-1123 published?

CVE-2006-1123 was published on 2006-03-09 and last updated on 2026-06-16.

CVE-2006-1123

CVE-2006-1123 is a critical-severity vulnerability in D2ksoft D2kblog with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: D2ksoft D2kblog
Published: 2006-03-09
Last modified: 2026-06-16

Description

SQL injection vulnerability in D2KBlog 1.0.3 and earlier allows remote attackers to execute arbitrary SQL commands via the memName parameter in a cookie.

Frequently asked questions

What is CVE-2006-1123?: SQL injection vulnerability in D2KBlog 1.0.3 and earlier allows remote attackers to execute arbitrary SQL commands via the memName parameter in a cookie.
How severe is CVE-2006-1123?: CVE-2006-1123 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2006-1123 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-1123?: CVE-2006-1123 primarily affects D2ksoft D2kblog. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-1123?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2006-1123 published?: CVE-2006-1123 was published on 2006-03-09 and last updated on 2026-06-16.

References

Affected products (4)

cpe:2.3:a:d2ksoft:d2kblog:1.0:*:*:*:*:*:*:*
cpe:2.3:a:d2ksoft:d2kblog:1.0.1:*:*:*:*:*:*:*
cpe:2.3:a:d2ksoft:d2kblog:1.0.2:*:*:*:*:*:*:*
cpe:2.3:a:d2ksoft:d2kblog:1.0.3:*:*:*:*:*:*:*

More vulnerabilities in D2ksoft D2kblog

CVE-2006-1122 — Medium (CVSS 6.8): Cross-site scripting (XSS) vulnerability in Default.asp in D2KBlog 1.0.3 and earlier allows remote attackers to inject…

All CVEs affecting D2ksoft D2kblog →