vrana/adminer vulnerabilities
Database management in a single PHP file.
- Registry
- Composer
- Latest
- 6.3.0
- License
- Apache-2.0, GPL-2.0-only
8 known advisories
The latest version, 6.3.0, is not affected by any of them. Projects on older versions may be.
composer require vrana/adminer:^6.3.0Is your project on an affected vrana/adminer?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for vrana/adminer
Adminer has an Unauthenticated Persistent DoS via Array Injection in ?script=version Endpoint
- Affected
- >=4.6.2 <5.4.2
- Fixed in
- 5.4.2
Adminer PHP Object Injection issue leads to Denial of Service
- Affected
- <=4.8.1
- Fixed in
- No fix released
Adminer file disclosure vulnerability
- Affected
- >=4.3.1 <4.6.3
- Fixed in
- 4.6.3
Files or Directories Accessible to External Parties in Adminer
- Affected
- >=1.12.0 <4.6.3
- Fixed in
- 4.6.3
XSS in doc_link
- Affected
- >=4.7.8 <4.8.1
- Fixed in
- 4.8.1
vrana/adminer vulnerable to SSRF by connecting to privileged ports
- Affected
- <4.7.8
- Fixed in
- 4.7.8
SSRF in adminer
- Affected
- <4.7.9
- Fixed in
- 4.7.9
vrana/adminer via XSS in the history parameter in SQL command
- Affected
- <4.7.9
- Fixed in
- 4.7.9
Is your vrana/adminer version vulnerable?
- vrana/adminer 6.3No known advisories in 6.3.0
- vrana/adminer 6.2No known advisories in 6.2.0
- vrana/adminer 6.1No known advisories in 6.1.2
- vrana/adminer 6.0No known advisories in 6.0.2
- vrana/adminer 5.5No known advisories in 5.5.1
- vrana/adminer 5.4No known advisories in 5.4.4
- vrana/adminer 5.31 advisory in 5.3.0
- vrana/adminer 5.21 advisory in 5.2.1
- vrana/adminer 5.11 advisory in 5.1.1
- vrana/adminer 5.01 advisory in 5.0.6
- vrana/adminer 4.171 advisory in 4.17.1
- vrana/adminer 4.161 advisory in 4.16.0
- vrana/adminer 4.141 advisory in 4.14.0
- vrana/adminer 4.131 advisory in 4.13.0
- vrana/adminer 4.121 advisory in 4.12.0
- vrana/adminer 4.111 advisory in 4.11.0
Which of your client projects still run an old vrana/adminer?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.