LaravelFramework / library
CVE-2020-24941
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Laravel before 6.18.35 and 7.x before 7.24.0. The $guarded property is mishandled in some situations involving requests with JSON column nesting expressions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceLaravel's mass assignment protection via the $guarded property fails to properly handle requests containing JSON column nesting expressions. This allows attackers to potentially bypass the $guarded restrictions and assign values to protected fields that should be protected from mass assignment, leading to unauthorized data modification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LaravelFramework / library
< 6.18.35>= 7.0.0, < 7.24.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Laravel versionRun 'php artisan --version' or check the 'laravel/framework' version in your composer.lock fileAffected if The installed version is below 6.18.35, or between 7.0.0 and 7.23.x
-
Identify models using $guardedSearch your codebase for 'protected $guarded' declarations in app/Models or app directoryAffected if Any Eloquent models define the $guarded property
-
Check for JSON column attributes in guarded modelsReview each $guarded model and identify if it accesses JSON columns (using -> operator or attributes casting to array/object)Affected if Guarded models contain JSON column attributes that accept user input
-
Audit mass assignment calls with user inputSearch for Model::create() and $model->fill() calls that accept request()->all(), request()->input(), or direct user-controlled arraysAffected if User input is passed directly to mass assignment methods on models with $guarded and JSON columns
-
Review controller logic for JSON payload handlingInspect controllers receiving JSON API requests (Content-Type: application/json) that flow into Eloquent modelsAffected if JSON request payloads containing nested keys like 'field->subfield' are accepted and passed to mass assignment methods
You are affected if your Laravel version is below 6.18.35 or between 7.0.0 and 7.23.x AND you use $guarded models that handle JSON columns with user-supplied input through mass assignment methods.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data6.18.357.24.0
Upgrade Laravel to version 6.18.35 or 7.24.0 or later to receive the patch. Additionally, review all Eloquent models using $guarded with JSON column attributes and implement explicit validation for any user-controlled input targeting those fields.
Fix this in Laravel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-24941 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data