{"answers":{"affected":"6 open source packages ship an affected version, including laravel/framework.","exploited":"There is no known exploitation of GHSA-44pg-c29v-hp6r in the wild and no public exploit code.","fix":"Upgrade laravel/framework to a fixed version for your release line: 6.18.34 or 7.23.2.","what":"GHSA-44pg-c29v-hp6r is a missing authorization vulnerability in laravel/framework, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-44pg-c29v-hp6r and fix it if it is affected.\n\nWhat it is: GHSA-44pg-c29v-hp6r is a missing authorization vulnerability in laravel/framework, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-44pg-c29v-hp6r in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- laravel/framework (Packagist): affected from 5.5.0 up to 5.5.49; no fix listed\n- laravel/framework (Packagist): affected from 5.5.0 up to 5.5.49; no fix listed\n- laravel/framework (Packagist): affected from 6.0.0; fixed in 6.18.34\n- laravel/framework (Packagist): affected from 6.0.0; fixed in 6.18.34\n- laravel/framework (Packagist): affected from 7.0.0; fixed in 7.23.2\n- laravel/framework (Packagist): affected from 7.0.0; fixed in 7.23.2\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-44pg-c29v-hp6r/ (Markdown: https://insights.sbomify.com/GHSA-44pg-c29v-hp6r/index.md)","id":"GHSA-44pg-c29v-hp6r","markdown":"https://insights.sbomify.com/GHSA-44pg-c29v-hp6r/index.md","name":"GHSA-44pg-c29v-hp6r","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel PHP framework","requires_auth":"low_privilege","summary":"Attackers can bypass mass assignment guards to modify protected database fields by using table-prefixed attribute names in Laravel applications.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:\n```\n$model-\u003efill(['users.name' =\u003e 'Taylor']);\n```\nWhen doing so, Eloquent would remove the table name from the attribute for you. This was a \"convenience\" feature of Eloquent and was not documented.\n\nHowever, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical \"fillable\" / \"guarded\" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.\n\nThis security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.","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":"Laravel Guard bypass in Eloquent models","id":"GHSA-44pg-c29v-hp6r","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":6,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["5.5.0"],"last_affected":["5.5.49"],"package":"laravel/framework","purl":null,"source":"GHSA-44pg-c29v-hp6r"},{"ecosystem":"Packagist","fixed":[],"introduced":["5.5.0"],"last_affected":["5.5.49"],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-44pg-c29v-hp6r"},{"ecosystem":"Packagist","fixed":["6.18.34"],"introduced":["6.0.0"],"last_affected":[],"package":"laravel/framework","purl":null,"source":"GHSA-44pg-c29v-hp6r"},{"ecosystem":"Packagist","fixed":["6.18.34"],"introduced":["6.0.0"],"last_affected":[],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-44pg-c29v-hp6r"},{"ecosystem":"Packagist","fixed":["7.23.2"],"introduced":["7.0.0"],"last_affected":[],"package":"laravel/framework","purl":null,"source":"GHSA-44pg-c29v-hp6r"},{"ecosystem":"Packagist","fixed":["7.23.2"],"introduced":["7.0.0"],"last_affected":[],"package":"laravel/framework","purl":"pkg:composer/laravel/framework","source":"GHSA-44pg-c29v-hp6r"}],"products":null,"published":"2024-05-15","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":"Attackers can bypass mass assignment guards to modify protected database fields by using table-prefixed attribute names in Laravel applications.","url":"https://insights.sbomify.com/GHSA-44pg-c29v-hp6r/"}