Is vrana/adminer vulnerable?

Composer vrana/adminer has 9 known advisories in the phpwarden feed, 1 actively exploited. Feed 2026.10.29.2, updated 2026-10-29.

9advisories
0critical
1on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2021-21311 KEVSSRF in adminerhigh7.2<4.7.94.7.9
CVE-2021-43008Files or Directories Accessible to External Parties in Adminerhigh7.5>=1.12.0 and <4.6.34.6.3
CVE-2021-29625XSS in doc_linkhigh7.5>=4.7.8 and <4.8.14.8.1
CVE-2018-7667vrana/adminer vulnerable to SSRF by connecting to privileged portsmedium0.0<4.7.84.7.8
CVE-2020-35572vrana/adminer via XSS in the history parameter in SQL commandmedium6.1<4.7.94.7.9
CVE-2026-25892Adminer has an Unauthenticated Persistent DoS via Array Injection in ?script=version Endpointhigh7.5>=4.6.2 and <5.4.25.4.2
CVE-2025-43960Adminer PHP Object Injection issue leads to Denial of Servicehigh8.6<=4.8.1–
GHSA-97h7-mf38-g9mfAdminer file disclosure vulnerabilityhigh7.5>=4.3.1 and <4.6.34.6.3
2019-01-20Adminer script versions up to 4.6.2 contains file disclosure vulnerabilityunknown0.0<4.6.34.6.3

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.