How severe is CVE-2006-1804?

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

Is CVE-2006-1804 being actively exploited?

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

What products are affected by CVE-2006-1804?

CVE-2006-1804 primarily affects Phpmyadmin. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-1804?

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

CVE-2006-1804 was published on 2006-04-18 and last updated on 2026-06-16.

CVE-2006-1804

CVE-2006-1804 is a high-severity vulnerability in Phpmyadmin 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% (70th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Phpmyadmin
Published: 2006-04-18
Last modified: 2026-06-16

Description

SQL injection vulnerability in sql.php in phpMyAdmin 2.7.0-pl1 allows remote attackers to execute arbitrary SQL commands via the sql_query parameter.

Frequently asked questions

What is CVE-2006-1804?: SQL injection vulnerability in sql.php in phpMyAdmin 2.7.0-pl1 allows remote attackers to execute arbitrary SQL commands via the sql_query parameter.
How severe is CVE-2006-1804?: CVE-2006-1804 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-1804 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-1804?: CVE-2006-1804 primarily affects Phpmyadmin. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-1804?: 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-1804 published?: CVE-2006-1804 was published on 2006-04-18 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:phpmyadmin:phpmyadmin:2.7.0_pl1:*:*:*:*:*:*:*
cpe:2.3:a:phpmyadmin:phpmyadmin:2.8.0.3:*:*:*:*:*:*:*

More vulnerabilities in Phpmyadmin

CVE-2008-7252 — Critical (CVSS 10.0): libraries/File.class.php in phpMyAdmin 2.11.x before 2.11.10 uses predictable filenames for temporary files, which has…
CVE-2008-7251 — Critical (CVSS 10.0): libraries/File.class.php in phpMyAdmin 2.11.x before 2.11.10 creates a temporary directory with 0777 permissions, which…
CVE-2007-0203 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in phpMyAdmin before 2.9.2-rc1 have unknown impact and attack vectors.
CVE-2004-1147 — Critical (CVSS 10.0): phpMyAdmin 2.6.0-pl2, and other versions before 2.6.1, with external transformations enabled, allows remote attackers…
CVE-2020-22452 — Critical (CVSS 9.8): SQL Injection vulnerability in function getTableCreationQuery in CreateAddField.php in phpMyAdmin 5.x before 5.2.0 via…
CVE-2020-26935 — Critical (CVSS 9.8): An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3. A SQL injection…

All CVEs affecting Phpmyadmin →