CVE-2006-1123: SQL injection vulnerability in D2KBlog 1.0.3 and earlier allows remote attackers to execute arbitrary SQL comm

This week

HIGH 10.0DOWNGRADE

CVE-2006-1123 is a high-severity flaw (CVSS 10.0) affecting d2kblog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Published	2006-03-09
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: d2ksoft

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2006-03-09 21:02 UTCPublished CVE record published
2026-06-16 22:22 UTCUpdated Record last modified

d2ksoft d2kblog DOWNGRADE

Affected: 1.0 · 1.0.1 · 1.0.2 · 1.0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy d2kblog || rpm -q d2kblog || d2kblog --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison d2kblog sudo apt install d2kblog=<VERSION_BEFORE_1.0> sudo apt-mark hold d2kblog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list d2kblog sudo dnf downgrade d2kblog-<VERSION_BEFORE_1.0> sudo dnf versionlock add d2kblog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: d2kBlog 1.0.3 - 'memName' SQL Injection

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-1123?

d2kblog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-1123 being exploited?

CVE-2006-1123 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-1123 affect?

CVE-2006-1123 affects d2kblog. Severity is high (CVSS 10.0). 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 urgent is CVE-2006-1123?

Priority 60/100. Critical severity; Public exploit reference

Related CVEs

CVE-2006-1122 MEDIUM 6.8 DOWNGRADE Cross-site scripting (XSS) vulnerability in Default.asp in D2KBlog 1.0.3 and earlier allows remote attackers t

References

← Back to latest CVEs