CVE-2006-0349: SQL injection vulnerability in eggblog 2.0 allows remote attackers to execute arbitrary SQL commands via the i

This month

HIGH 7.5DOWNGRADE

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

SQL injection vulnerability in eggblog 2.0 allows remote attackers to execute arbitrary SQL commands via the id parameter to blog.php.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Published	2006-01-21
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: epic designs

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

Am I affected?

Timeline

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

epic designs eggblog DOWNGRADE

Affected: 2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

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

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

apt-cache madison eggblog sudo apt install eggblog=<VERSION_BEFORE_2.0> sudo apt-mark hold eggblog

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

dnf --showduplicates list eggblog sudo dnf downgrade eggblog-<VERSION_BEFORE_2.0> sudo dnf versionlock add eggblog

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: EggBlog 2.0 - 'id' 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-0349?

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

Is CVE-2006-0349 being exploited?

CVE-2006-0349 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-0349 affect?

CVE-2006-0349 affects eggblog. Severity is high (CVSS 7.5). SQL injection vulnerability in eggblog 2.0 allows remote attackers to execute arbitrary SQL commands via the id parameter to blog.php.

How urgent is CVE-2006-0349?

Priority 49/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2011-3732 MEDIUM 5.0 DOWNGRADE eggBlog 4.1.2 allows remote attackers to obtain sensitive information via a direct request to a .php file, whi
CVE-2008-1626 HIGH 7.5 UPGRADE SQL injection vulnerability in eggBlog before 4.0.1 allows remote attackers to execute arbitrary SQL commands
CVE-2008-0159 MEDIUM 6.8 UPGRADE SQL injection vulnerability in index.php in eggBlog 3.1.0 and earlier allows remote attackers to execute arbit
CVE-2007-5980 MEDIUM 4.3 UPGRADE Cross-site scripting (XSS) vulnerability in home/rss.php in eggblog before 3.1.1 allows remote attackers to in
CVE-2007-2978 MEDIUM 6.8 UPGRADE Session fixation vulnerability in eggblog 3.1.0 and earlier allows remote attackers to hijack web sessions by

References

← Back to latest CVEs