illuminate/database vulnerabilities

The Illuminate Database package.

Registry
Composer
Latest
13.38.0
License
MIT

5 known advisories

The latest version, 13.38.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require illuminate/database:^13.38.0

Security advisories for illuminate/database

  • MediumGHSA-cc2w-ghc5-m5qr15 May 2024

    Laravel Risk of mass-assignment vulnerabilities

    Affected
    >=4.0.0 <4.1.29
    Fixed in
    4.1.29
  • HighGHSA-c7rm-w2hj-x8g324 May 2022

    Guard bypass in Eloquent models affecting Laravel illuminate database component

    Affected
    >=5.5.0 <=5.5.44 · >=6.0.0 <6.18.34 · >=7.0.0 <7.23.2
    Fixed in
    6.18.34, 7.23.2
  • HighGHSA-4mg9-vhxq-vm7j29 Apr 2021

    SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/database

    Affected
    >=8.0.0 <8.40.0 · <6.20.26
    Fixed in
    6.20.26, 8.40.0
  • HighGHSA-x7p5-p2c9-phvg2 Feb 2021

    Unexpected database bindings

    Affected
    <6.20.14 · >=7.0.0 <7.30.4 · >=8.0.0 <8.24.0
    Fixed in
    6.20.14, 7.30.4, 8.24.0
  • HighGHSA-3p32-j457-pg5x19 Jan 2021

    Query Binding Exploitation

    Affected
    >=7.0.0 <7.30.3 · >=8.0.0 <8.22.1 · >=6.0.0 <6.20.12
    Fixed in
    6.20.12, 7.30.3, 8.22.1

Which of your client projects still run an old illuminate/database?

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.