How to Fix Missing Rate Limiting in Laravel
Learn how to prevent and fix Missing Rate Limiting vulnerabilities in Laravel applications. Step-by-step guide with code examples, security checklists, and best practices.
What Is Missing Rate Limiting?
Missing Rate Limiting is a vulnerability where an application does not restrict the number or frequency of requests a user or client can make to a particular endpoint or resource. Without rate limits, there is no mechanism to prevent abuse of API endpoints, authentication forms, or resource-intensive operations.
This vulnerability is particularly relevant for: login and authentication endpoints (allowing brute force attacks); password reset and OTP verification endpoints (allowing enumeration and bypasses); API endpoints that return sensitive data (allowing mass data harvesting); resource-intensive operations like file processing or report generation (allowing resource exhaustion); and endpoints that send emails or SMS messages (allowing spam or cost amplification).
In serverless and edge environments (Vercel, Cloudflare Workers), traditional rate limiting using in-memory counters does not work because each request may be handled by a different instance. Applications in these environments need distributed rate limiting using external stores like Redis, Upstash, or purpose-built services.
Why It Matters
Without rate limiting, attackers can automate attacks at scale. Credential stuffing attacks can try thousands of username/password combinations per second. API abuse can extract large volumes of data or incur significant compute costs. Brute force attacks on OTP codes or short tokens become feasible. Denial of service attacks can overwhelm backend resources. For SaaS applications, missing rate limits can lead to unexpected infrastructure costs as attackers consume compute, bandwidth, and third-party API quotas. Rate limiting is also a requirement for compliance with many security standards.
How to Fix It in Laravel
Implement rate limiting on all externally accessible endpoints, with stricter limits on authentication and sensitive operations. Use a distributed rate limiting solution (Upstash, Redis) for serverless deployments. Apply different rate limit tiers based on authentication status and user role. Implement exponential backoff for failed authentication attempts. Use CAPTCHA as a secondary defense for endpoints under heavy abuse. Return appropriate HTTP 429 (Too Many Requests) responses with Retry-After headers. Monitor rate limit hits to detect attack patterns. Consider using an API gateway (Kong, AWS API Gateway) that provides built-in rate limiting. Implement per-user, per-IP, and global rate limits as separate layers.
Laravel-Specific Advice
- Blade templates auto-escape output with `{{ }}`. Never use `{!! !!}` (unescaped output) with unsanitized user input.
- Use Eloquent ORM or Query Builder with parameter binding. Never concatenate user input into raw DB queries.
- Laravel includes CSRF protection by default via the `VerifyCsrfToken` middleware. Ensure all forms include `@csrf`.
- Use Laravel's built-in validation (`$request->validate()`) for all incoming data. Define strict validation rules.
Laravel Security Checklist for Missing Rate Limiting
Laravel Security Best Practices
Blade templates auto-escape output with `{{ }}`. Never use `{!! !!}` (unescaped output) with unsanitized user input.
Use Eloquent ORM or Query Builder with parameter binding. Never concatenate user input into raw DB queries.
Laravel includes CSRF protection by default via the `VerifyCsrfToken` middleware. Ensure all forms include `@csrf`.
Use Laravel's built-in validation (`$request->validate()`) for all incoming data. Define strict validation rules.
Configure `APP_DEBUG=false` in production. Debug mode exposes sensitive application details and stack traces.
Use Laravel's `Hash` facade (bcrypt by default) for password hashing. Never store passwords in plain text.
Use Laravel's rate limiting middleware (`throttle`) on routes, especially authentication endpoints.
Use `php artisan key:generate` to set `APP_KEY` and keep it secret. This key encrypts cookies and signed URLs.
Scan Your Laravel App with SafeVibe
Stop guessing if your Laravel app is vulnerable to Missing Rate Limiting. Run an automated penetration test in minutes and get actionable results.
Start Free Scan