{"answers":{"affected":"8 open source packages ship an affected version, including illuminate/database and laravel/framework.","exploited":"There is no known exploitation of GHSA-4mg9-vhxq-vm7j in the wild and no public exploit code.","fix":"Upgrade illuminate/database to a fixed version for your release line: 6.20.26 or 8.40.0.","what":"GHSA-4mg9-vhxq-vm7j is a SQL injection vulnerability in illuminate/database, published on 29 Apr 2021. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-4mg9-vhxq-vm7j and fix it if it is affected.\n\nWhat it is: GHSA-4mg9-vhxq-vm7j is a SQL injection vulnerability in illuminate/database, published on 29 Apr 2021. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-4mg9-vhxq-vm7j in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- illuminate/database (Packagist): affected all versions; fixed in 6.20.26\n- illuminate/database (Packagist): affected all versions; fixed in 6.20.26\n- illuminate/database (Packagist): affected from 8.0.0; fixed in 8.40.0\n- illuminate/database (Packagist): affected from 8.0.0; fixed in 8.40.0\n- laravel/framework (Packagist): affected all versions; fixed in 6.20.26\n- laravel/framework (Packagist): affected all versions; fixed in 6.20.26\n- laravel/framework (Packagist): affected from 8.0.0; fixed in 8.40.0\n- laravel/framework (Packagist): affected from 8.0.0; fixed in 8.40.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-4mg9-vhxq-vm7j/ (Markdown: https://insights.sbomify.com/GHSA-4mg9-vhxq-vm7j/index.md)","id":"GHSA-4mg9-vhxq-vm7j","markdown":"https://insights.sbomify.com/GHSA-4mg9-vhxq-vm7j/index.md","name":"GHSA-4mg9-vhxq-vm7j","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Laravel framework","requires_auth":"unknown","summary":"SQL injection vulnerability in Laravel when using SQL Server with user-controlled limit and offset parameters, allowing unauthorized database access.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nThose using SQL Server with Laravel and allowing user input to be passed directly to the `limit` and `offset` functions are vulnerable to SQL injection. Other database drivers such as MySQL and Postgres are not affected by this vulnerability.\n\n### Patches\n\nThis problem has been patched on Laravel versions 6.20.26, 7.30.5, and 8.40.0.\n\n### Workarounds\n\nYou may workaround this vulnerability by ensuring that only integers are passed to the `limit` and `offset` functions, as well as the `skip` and `take` functions.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/database","id":"GHSA-4mg9-vhxq-vm7j","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2021"},"n_packages":8,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["6.20.26"],"introduced":["0"],"last_affected":[],"package":"illuminate/database","purl":null,"source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["6.20.26"],"introduced":["0"],"last_affected":[],"package":"illuminate/database","purl":"pkg:composer/illuminate/database","source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["8.40.0"],"introduced":["8.0.0"],"last_affected":[],"package":"illuminate/database","purl":null,"source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["8.40.0"],"introduced":["8.0.0"],"last_affected":[],"package":"illuminate/database","purl":"pkg:composer/illuminate/database","source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["6.20.26"],"introduced":["0"],"last_affected":[],"package":"laravel/framework","purl":null,"source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["6.20.26"],"introduced":["0"],"last_affected":[],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["8.40.0"],"introduced":["8.0.0"],"last_affected":[],"package":"laravel/framework","purl":null,"source":"GHSA-4mg9-vhxq-vm7j"},{"ecosystem":"Packagist","fixed":["8.40.0"],"introduced":["8.0.0"],"last_affected":[],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-4mg9-vhxq-vm7j"}],"products":null,"published":"2021-04-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"SQL injection vulnerability in Laravel when using SQL Server with user-controlled limit and offset parameters, allowing unauthorized database access.","url":"https://insights.sbomify.com/GHSA-4mg9-vhxq-vm7j/"}