Vulnerability Database · Debian · Package report

phpmyadmin: vulnerability history, versions and safety

phpmyadmin is a package in the Debian ecosystem. Vulert records 457 vulnerabilities for it across 29 releases, from Mar 2004 to Apr 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
457 vulnerabilities recorded U457
i
9 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on phpmyadmin i

Updated on 23 Oct 2026

Careful: 9 of the 457 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 457 vulnerabilities on record across 21 years, none in the last year.

What to do: Plan around the 9 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 457 over 21 years · 0 in the last year i
  • Latest disclosure 08 Apr 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 9 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for phpmyadmin, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 29 of 29 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2004 8
  • 2005 36
  • 2006 24
  • 2007 34
  • 2008 22
  • 2009 16
  • 2010 20
  • 2011 34
  • 2012 14
  • 2013 26
  • 2014 40
  • 2015 12
  • 2016 103
  • 2017 14
  • 2018 14
  • 2019 14
  • 2020 14
  • 2022 3
  • 2023 4
  • 2025 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 457 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for phpmyadmin

The 5 most severe of 457 vulnerabilities recorded for this package

Search all 457 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About phpmyadmin

Is phpmyadmin safe to use?

Vulert records 457 vulnerabilities for phpmyadmin in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 457 not yet rated. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does phpmyadmin have?

457 vulnerabilities are recorded for phpmyadmin in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 457 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new phpmyadmin vulnerabilities disclosed?

0 vulnerabilities were recorded for phpmyadmin in the last 12 months, and the oldest entry in this database dates to 03 Mar 2004. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of phpmyadmin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor phpmyadmin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the phpmyadmin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.