CVE-2005-4349

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

Score 6.3 from GitHub Security Advisory published 2022-05-01. NVD baseline CVSS 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SQL injection vulnerability in server_privileges.php in phpMyAdmin 2.7.0 allows remote authenticated users to execute arbitrary SQL commands via the (1) dbname and (2) checkprivs parameters. NOTE: the vendor and a third party have disputed this issue, saying that the main task of the program is to support query execution by authenticated users, and no external attack scenario exists without an auto-login configuration. Thus it is likely that this issue will be REJECTED. However, a closely related CSRF issue has been assigned CVE-2005-4450

CVSS v3
6.3
EG Score
6.3(medium)
EPSS
69.1%
KEV
Not listed

Published

December 19, 2005

Last Modified

April 16, 2026

Advisory Details (6)

Auto-updated May 31, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

phpMyAdmin server_privileges.php SQL Injection Vulnerabilities. - CXSecurity.com

http://securityreason.com/securityalert/270
generic

About Secunia Research | Flexera

http://secunia.com/advisories/18113
generic🟡 PoC Available

'phpMyAdmin server_privileges.php SQL Injection Vulnerabilities.' - MARC

http://marc.info/?l=bugtraq&m=113486637512821&w=2
generic

VUPEN Security - Vulnerability Research and Intelligence

http://www.vupen.com/english/advisories/2005/2995

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:24 UTCEPSS rescore
  2. 2026-07-13 06:07 UTCEPSS rescore
  3. 2026-07-13 06:07 UTCEPSS rescore
  4. 2026-07-11 08:22 UTCEPSS rescore
  5. 2026-07-11 08:22 UTCEPSS rescore
  6. 2026-07-09 02:09 UTCOSV refresh
  7. 2026-07-08 15:09 UTCEPSS rescore
  8. 2026-07-06 02:19 UTCEPSS rescore
  9. 2026-07-06 02:19 UTCEPSS rescore
  10. 2026-07-02 14:00 UTCEPSS rescore
  11. 2026-07-01 15:01 UTCEPSS rescore
  12. 2026-06-29 14:02 UTCEPSS rescore
  13. 2026-06-29 14:02 UTCEPSS rescore
  14. 2026-06-28 04:52 UTCEPSS rescore
  15. 2026-06-27 03:04 UTCEPSS rescore
  16. 2026-06-25 13:46 UTCEPSS rescore
  17. 2026-06-24 14:01 UTCEPSS rescore
  18. 2026-06-23 21:29 UTCEPSS rescore
  19. 2026-06-22 14:22 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-21 01:56 UTCEPSS rescore
  22. 2026-06-20 14:12 UTCOSV refresh
  23. 2026-06-19 19:22 UTCEPSS rescore
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-18 17:49 UTCEPSS rescore
Show 48 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-17 17:49 UTCEPSS rescore
  3. 2026-06-16 17:49 UTCEPSS rescore
  4. 2026-06-16 17:49 UTCEPSS rescore
  5. 2026-06-15 17:44 UTCEPSS rescore
  6. 2026-06-14 23:13 UTCEPSS rescore
  7. 2026-06-14 23:13 UTCEPSS rescore
  8. 2026-06-13 22:56 UTCEPSS rescore
  9. 2026-06-12 23:08 UTCEPSS rescore
  10. 2026-06-11 13:55 UTCEPSS rescore
  11. 2026-06-10 22:14 UTCEPSS rescore
  12. 2026-06-10 13:17 UTCEPSS rescore
  13. 2026-06-08 14:13 UTCEPSS rescore
  14. 2026-06-07 15:21 UTCEPSS rescore
  15. 2026-06-06 13:44 UTCEPSS rescore
  16. 2026-06-06 13:44 UTCEPSS rescore
  17. 2026-06-05 22:43 UTCEPSS rescore
  18. 2026-06-05 22:43 UTCEPSS rescore
  19. 2026-06-05 06:07 UTCEPSS rescore
  20. 2026-06-05 06:07 UTCEPSS rescore
  21. 2026-06-04 13:09 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 11:04 UTCEG score recompute
  29. 2026-05-31 11:04 UTCGHSA enrichment
  30. 2026-05-31 00:13 UTCEPSS rescore
  31. 2026-05-31 00:13 UTCEPSS rescore
  32. 2026-05-29 13:40 UTCEPSS rescore
  33. 2026-05-29 13:40 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-27 13:37 UTCEPSS rescore
  38. 2026-05-26 13:41 UTCEPSS rescore
  39. 2026-05-26 13:41 UTCEPSS rescore
  40. 2026-05-24 16:42 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-21 22:38 UTCEPSS rescore
  43. 2026-05-20 23:06 UTCOSV refresh
  44. 2026-05-20 22:36 UTCEPSS rescore
  45. 2026-05-20 22:36 UTCEPSS rescore
  46. 2026-05-20 11:20 UTCEPSS rescore
  47. 2026-05-20 11:20 UTCEPSS rescore
  48. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2005-4349?
CVE-2005-4349 is a medium vulnerability published on December 19, 2005. SQL injection vulnerability in server_privileges.php in phpMyAdmin 2.7.0 allows remote authenticated users to execute arbitrary SQL commands via the (1) dbname and (2) checkprivs parameters. NOTE: the vendor and a third party have disputed this issue, saying that the main task of the program is to…
When was CVE-2005-4349 disclosed?
CVE-2005-4349 was first published in the National Vulnerability Database on December 19, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-4349 actively exploited?
CVE-2005-4349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 69.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2005-4349?
CVE-2005-4349 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2005-4349?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-4349, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-4349

Explore →

Is Your Infrastructure Affected by CVE-2005-4349?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.