How severe is GHSA-cc2w-ghc5-m5qr?

No CVSS score has been assigned to GHSA-cc2w-ghc5-m5qr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cc2w-ghc5-m5qr?

GHSA-cc2w-ghc5-m5qr affects the following packages: illuminate/database (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cc2w-ghc5-m5qr?

Update illuminate/database to 4.1.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cc2w-ghc5-m5qr is resolved across your whole dependency graph.

How do I detect GHSA-cc2w-ghc5-m5qr in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for illuminate/database, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cc2w-ghc5-m5qr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-cc2w-ghc5-m5qr actively exploited in the wild?

No public exploit code has been indexed for GHSA-cc2w-ghc5-m5qr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-cc2w-ghc5-m5qr published, and has it been updated?

GHSA-cc2w-ghc5-m5qr was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Laravel Risk of mass-assignment vulnerabilities

Real-World Exposure

1 pkg affected

🐘illuminate/database

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Laravel 4.1.29 improves the column quoting for all database drivers. This protects your application from some mass assignment vulnerabilities when not using the fillable property on models. If you are using the fillable property on your models to protect against mass assignment, your application is not vulnerable. However, if you are using guarded and are passing a user controlled array into an "update" or "save" type function, you should upgrade to 4.1.29 immediately as your application may be at risk of mass assignment.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`illuminate/database`	≥ 4.0.0&&< 4.1.29	4.1.29`composer require illuminate/database:^4.1.29`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for illuminate/database, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update illuminate/database to 4.1.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cc2w-ghc5-m5qr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Laravel 4.1.29 improves the column quoting for all database drivers. This protects your application from some mass assignment vulnerabilities when not using the fillable property on models. If you are using the fillable property on your models to protect against mass assignment, your application is not vulnerable. However, if you are using guarded and are passing a user controlled array into an "update" or "save" type function, you should upgrade to 4.1.29 immediately as your application may be at risk of mass assignment.

O3 Security · Impact-Aware SCA

Is GHSA-cc2w-ghc5-m5qr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Laravel Risk of mass-assignment vulnerabilitiesGHSA-cc2w-ghc5-m5qr