Skip to main content
Platform security guideReviewed

Laravel security: the settings, dashboards and routes to check

Laravel ships defences for CSRF, mass assignment and authorisation, and each one depends on settings and code your team controls.

This guide sets out what Laravel's own documentation and the Debugbar readme say about debug mode, APP_KEY, Telescope, Horizon, Debugbar, signed URLs, file storage and queues, and gives you an evidence sheet to fill in for your own application.

Laravel configuration evidence sheet

Paste the table into a spreadsheet and save a separate workbook for each environment the internet can reach. Rows 1 to 12 are readings: look where the third column says and write down what the fourth asks for, without changing anything.

How to use it

Rows 13 to 15 are tests for a staging copy you control, with test accounts A and B in the same role, a lower-role test account and records those accounts created. Never write a key, password or token into the sheet. The documentation column was checked against the Laravel 13.x documentation (and the 12.x CSRF page for row 14), the Debugbar readme and the advisory records on 14 November 2026.

15 rows

Laravel configuration evidence sheet

ItemWhat the documentation saysWhere to look, or what to doWhat to write down
1. Framework version and support windowRelease notes: for all Laravel releases, bug fixes are provided for 18 months and security fixes for 2 years, and the support table gives each version a "Security Fixes Until" date. The Security page of the laravel/framework repository lists the framework's published advisories.The laravel/framework entry in composer.lock for the commit that is deployed. The support table on the release notes page for your major version. The repository's Security page and the GitHub Advisory Database.The exact laravel/framework version and commit, the "Security Fixes Until" date for that major version, the date you read it, and the id of each advisory whose affected range includes your version.
2. APP_ENV in each environmentConfiguration page: the current environment is determined via the APP_ENV variable, and that detection can be overridden by defining a server-level APP_ENV variable. Telescope page: unless APP_ENV is production in production, the Telescope installation will be publicly available. GHSA-gv7v-rgg6-548h (CVE-2024-52301): with register_argc_argv on, a crafted query string can change the environment the framework uses; the advisory lists the affected and patched versions.Where your host or deployment pipeline sets each environment's variables, and the .env file only where nothing overrides it. The configuration page documents php artisan about --only=environment for the environment section of Laravel's overview. The register_argc_argv setting in the PHP configuration the web server uses.The APP_ENV value for each environment, where it is set and who can change it, the register_argc_argv value, and your laravel/framework version against the patched versions in GHSA-gv7v-rgg6-548h.
3. APP_DEBUG in every internet-reachable environmentConfiguration and deployment pages: the debug option decides how much error information is displayed; in production it should always be false, and true risks exposing sensitive configuration values to end users. The configuration page prints the default line as env('APP_DEBUG', false) and says the second value is returned if no environment variable exists for the key. GHSA-jh5r-qr3c-85q8 and CVE-2021-3129 each name debug mode as a condition.The APP_DEBUG value in each environment's variables, staging and preview copies included, and the debug line in config/app.php. If the deployment runs config:cache, read the value again after each deploy.True or false for each environment, where it is set, the date checked, and whether facade/ignition or Debugbar is installed in the same environment.
4. APP_KEY and the environment fileEncryption page: APP_KEY drives the encryption key; changing it logs out all authenticated user sessions and leaves data encrypted with the old key undecryptable. To mitigate this, the page offers APP_PREVIOUS_KEYS: Laravel tries each listed earlier key when the current one cannot decrypt a value. Configuration page: .env should not be committed to source control; an encrypted .env.encrypted file may be, with its decryption key in a secure password manager.The place each environment's variables are stored, the repository (whether .env is tracked, or only .env.example or .env.encrypted), and the access list for both. Check only whether each variable exists; do not open or display its value.For APP_KEY, APP_PREVIOUS_KEYS and LARAVEL_ENV_ENCRYPTION_KEY: set or not set, where stored, who can read it, and when it last changed if anyone knows. Never the value. This row does not rotate the key: the encryption page describes what a rotation changes, and it is planned with the application's owners.
5. Web server document rootDeployment page: the web server should direct all requests to public/index.php, and serving the application from the project root will expose many sensitive configuration files to the public internet.The document root in the web server or hosting panel configuration for each site and environment.The document root path for each environment, and whether it ends in the application's public directory.
6. TelescopeTelescope page: records requests with their headers, session and response data, exceptions, logs, queries with bindings, jobs, mail and more. /telescope opens only in the local environment by default; the viewTelescope gate in app/Providers/TelescopeServiceProvider.php controls access elsewhere. A local-only installation uses --dev, removes the provider registration from bootstrap/providers.php, registers the providers in AppServiceProvider only when the environment is local and adds laravel/telescope to dont-discover. Once telescope:prune is scheduled, entries older than 24 hours are pruned by default.composer.json (require or require-dev, and the dont-discover list), bootstrap/providers.php, app/Providers/AppServiceProvider.php, app/Providers/TelescopeServiceProvider.php, config/telescope.php and the schedule.Installed in production or not, and in which composer.json section; the gate's rule in words (roles or named people, without copying email addresses); TELESCOPE_ENABLED in each environment; whether telescope:prune is scheduled and the retention it uses.
7. HorizonHorizon page: a dashboard for Redis queues at /horizon that opens only in the local environment by default; the viewHorizon gate in app/Providers/HorizonServiceProvider.php controls access elsewhere. An application that protects Horizon another way, such as IP restrictions, changes the gate closure to accept a null user, which forces Laravel not to require authentication.composer.json, app/Providers/HorizonServiceProvider.php, and any web server or firewall rule in front of /horizon.Installed or not; the gate's rule in words; whether the closure accepts a null user and, if it does, what restriction replaced the login and who maintains it.
8. DebugbarDebugbar readme (fruitcake/laravel-debugbar, formerly barryvdh/laravel-debugbar): use only in development and not on publicly accessible websites, as it will leak information from stored requests by design. Enabled when APP_DEBUG is true and the environment is not production or testing. DEBUGBAR_FORCE_ALLOW_ENABLE does not enable it but runs its service provider bootstrap so it can be enabled in production; the stored request history answers only localhost or a private network unless DEBUGBAR_OPEN_STORAGE changes that.composer.json and composer.lock (require or require-dev), config/debugbar.php if it has been published, and the DEBUGBAR_ENABLED, DEBUGBAR_FORCE_ALLOW_ENABLE and DEBUGBAR_OPEN_STORAGE variables in each environment.Package name, version and composer.json section, and the value of each of the three variables for each environment, or "not set".
9. Signed URLsURL generation page: a signature covers only the path and query string; any other request input, such as a form or JSON body, is not signed, and input read with any method other than query may return unsigned values that override signed ones. Ignored parameters can be changed by anyone. The signed middleware returns 403 for an invalid signature. GHSA-crmm-hgp2-wgrp, GHSA-v5ch-g375-82r6 and GHSA-6rv8-qj5v-p8ch concern temporary signed URL expiry.php artisan route:list -v for routes carrying the signed middleware, and a code search for signedRoute, temporarySignedRoute, hasValidSignature, hasValidSignatureWhileIgnoring and temporaryUrl.Each signed route, what it lets the holder do, its expiry, whether the handler reads signed values with the query method, any ignored parameters, whether request-derived arrays reach signed URL generation, and your framework version against each advisory's patched versions.
10. Storage disks and visibilityFile storage page: disks are set in config/filesystems.php. The local disk's root defaults to storage/app/private. The public disk is intended for publicly accessible files; by default it uses the local driver and stores them in storage/app/public, and storage:link creates the public/storage link that makes them reachable from the web. On the local driver, public visibility translates to 0644 files and 0755 directories, a mapping the filesystems configuration file can change; storePublicly and storePubliclyAs store uploads as public.config/filesystems.php (each disk's driver, root and visibility, and the links list), and a code search for storePublicly, storePubliclyAs, setVisibility and uses of the public disk.Each disk with its driver, root and visibility, and the features that write to it. For each feature that stores customer files: public or private disk, and whether downloads go through a checked route or a temporary URL.
11. Queue connections and job dataQueues page: connections are set in config/queue.php. Instances of one application sharing a Redis server should each use their own key prefix or Redis database. ShouldBeEncrypted encrypts a job before it is pushed onto the queue. When a job accepts an Eloquent model in its constructor, only the model's identifier is serialised onto the queue. Asynchronous jobs that run out of attempts go to the failed_jobs table, and queue:prune-failed removes records older than 24 hours by default.config/queue.php and config/database.php (driver, host, prefix and database number, read without the passwords), the network rules around the queue backend, and the job classes.The queue driver and backend, what can reach it on the network, which credentials it uses (named, not copied), whether another instance or application shares it and with what prefix, which jobs carry personal or payment details and whether each implements ShouldBeEncrypted, and how long failed job records are kept.
12. Route and middleware inventoryRouting page: php artisan route:list lists the application's routes; -v adds each route's middleware and middleware group names, -vv expands the groups, and --except-vendor hides routes defined by third-party packages.Run route:list -v on a copy you control, once as it is and once with --except-vendor.For each route that reads or changes customer data: method and URI, whether it is in the web group, and whether it carries auth, can or signed middleware. Package routes such as /telescope and /horizon go on the list too.
13. Test: mass assignmentEloquent page: a model needs a Fillable or Guarded attribute before create can be used; attributes outside Fillable are silently discarded by default, and preventSilentlyDiscardingAttributes makes Laravel throw an exception instead; for an unguarded model, the page asks for special care to hand-craft every array passed to fill, create and update.On staging, signed in as test account A, open the edit form for one of A's own test records. In the browser's element inspector, add a field the form does not send, such as a role flag, an owner or team id, or a status column the model holds, submit, then open the record again.The route, the field added, whether the stored record changed, and the model's Fillable or Guarded list. A changed record is the finding; a silently discarded field, or an exception where the application calls preventSilentlyDiscardingAttributes, is the expected result.
14. Test: CSRFCSRF page (13.x): the PreventRequestForgery middleware in the web group lets a same-origin request through on the Sec-Fetch-Site header and by default falls back to the token check; in origin-only mode a request that fails origin verification gets a 403 response in place of the 419 typically associated with a token mismatch; Sec-Fetch-Site is sent only over HTTPS; allowSameSite admits same-site requests; the except list excludes URIs; the middleware is switched off automatically when tests run. The 12.x page describes token checks by ValidateCsrfToken and exclusions through validateCsrfTokens.Read the preventRequestForgery (13.x) or validateCsrfTokens (12.x) call in bootstrap/app.php and list each excluded URI and option. Then, on staging over HTTPS and signed in as test account A, submit a form to one of A's state-changing routes from a page on a different site you control, and open the test record.Each excluded URI and what protects it instead, whether allowSameSite or origin-only mode is set, the status code the cross-site submission received, and whether the record changed. A refusal with the record unchanged is the expected result.
15. Test: object authorisation and rolesAuthorisation page: a signed-in user may still not be allowed to update or delete a record. Ways to authorise an action with a policy include the can middleware, the User model's can and cannot methods and the Gate facade; when a gate or policy denies an action a 403 response is returned, and denyAsNotFound returns 404 instead. By default, gates and policies return false for a request from a user who is not signed in. @can in Blade decides what part of a page is displayed.On staging, test account A creates a record. Signed in as test account B, request A's record by changing its id on each view, edit, update and delete route. Signed in as the lower-role test account, request each administrator route, aimed only at records the test accounts created. Use no other records.For each route, method and account: the status code, whether any of A's data appeared, and whether the record changed. A 403 or 404 with nothing changed is the expected result.

Item

What the documentation says

  1. 1. Framework version and support window
    What the documentation says
    Release notes: for all Laravel releases, bug fixes are provided for 18 months and security fixes for 2 years, and the support table gives each version a "Security Fixes Until" date. The Security page of the laravel/framework repository lists the framework's published advisories.
    Where to look, or what to do
    The laravel/framework entry in composer.lock for the commit that is deployed. The support table on the release notes page for your major version. The repository's Security page and the GitHub Advisory Database.
    What to write down
    The exact laravel/framework version and commit, the "Security Fixes Until" date for that major version, the date you read it, and the id of each advisory whose affected range includes your version.
  2. 2. APP_ENV in each environment
    What the documentation says
    Configuration page: the current environment is determined via the APP_ENV variable, and that detection can be overridden by defining a server-level APP_ENV variable. Telescope page: unless APP_ENV is production in production, the Telescope installation will be publicly available. GHSA-gv7v-rgg6-548h (CVE-2024-52301): with register_argc_argv on, a crafted query string can change the environment the framework uses; the advisory lists the affected and patched versions.
    Where to look, or what to do
    Where your host or deployment pipeline sets each environment's variables, and the .env file only where nothing overrides it. The configuration page documents php artisan about --only=environment for the environment section of Laravel's overview. The register_argc_argv setting in the PHP configuration the web server uses.
    What to write down
    The APP_ENV value for each environment, where it is set and who can change it, the register_argc_argv value, and your laravel/framework version against the patched versions in GHSA-gv7v-rgg6-548h.
  3. 3. APP_DEBUG in every internet-reachable environment
    What the documentation says
    Configuration and deployment pages: the debug option decides how much error information is displayed; in production it should always be false, and true risks exposing sensitive configuration values to end users. The configuration page prints the default line as env('APP_DEBUG', false) and says the second value is returned if no environment variable exists for the key. GHSA-jh5r-qr3c-85q8 and CVE-2021-3129 each name debug mode as a condition.
    Where to look, or what to do
    The APP_DEBUG value in each environment's variables, staging and preview copies included, and the debug line in config/app.php. If the deployment runs config:cache, read the value again after each deploy.
    What to write down
    True or false for each environment, where it is set, the date checked, and whether facade/ignition or Debugbar is installed in the same environment.
  4. 4. APP_KEY and the environment file
    What the documentation says
    Encryption page: APP_KEY drives the encryption key; changing it logs out all authenticated user sessions and leaves data encrypted with the old key undecryptable. To mitigate this, the page offers APP_PREVIOUS_KEYS: Laravel tries each listed earlier key when the current one cannot decrypt a value. Configuration page: .env should not be committed to source control; an encrypted .env.encrypted file may be, with its decryption key in a secure password manager.
    Where to look, or what to do
    The place each environment's variables are stored, the repository (whether .env is tracked, or only .env.example or .env.encrypted), and the access list for both. Check only whether each variable exists; do not open or display its value.
    What to write down
    For APP_KEY, APP_PREVIOUS_KEYS and LARAVEL_ENV_ENCRYPTION_KEY: set or not set, where stored, who can read it, and when it last changed if anyone knows. Never the value. This row does not rotate the key: the encryption page describes what a rotation changes, and it is planned with the application's owners.
  5. 5. Web server document root
    What the documentation says
    Deployment page: the web server should direct all requests to public/index.php, and serving the application from the project root will expose many sensitive configuration files to the public internet.
    Where to look, or what to do
    The document root in the web server or hosting panel configuration for each site and environment.
    What to write down
    The document root path for each environment, and whether it ends in the application's public directory.
  6. 6. Telescope
    What the documentation says
    Telescope page: records requests with their headers, session and response data, exceptions, logs, queries with bindings, jobs, mail and more. /telescope opens only in the local environment by default; the viewTelescope gate in app/Providers/TelescopeServiceProvider.php controls access elsewhere. A local-only installation uses --dev, removes the provider registration from bootstrap/providers.php, registers the providers in AppServiceProvider only when the environment is local and adds laravel/telescope to dont-discover. Once telescope:prune is scheduled, entries older than 24 hours are pruned by default.
    Where to look, or what to do
    composer.json (require or require-dev, and the dont-discover list), bootstrap/providers.php, app/Providers/AppServiceProvider.php, app/Providers/TelescopeServiceProvider.php, config/telescope.php and the schedule.
    What to write down
    Installed in production or not, and in which composer.json section; the gate's rule in words (roles or named people, without copying email addresses); TELESCOPE_ENABLED in each environment; whether telescope:prune is scheduled and the retention it uses.
  7. 7. Horizon
    What the documentation says
    Horizon page: a dashboard for Redis queues at /horizon that opens only in the local environment by default; the viewHorizon gate in app/Providers/HorizonServiceProvider.php controls access elsewhere. An application that protects Horizon another way, such as IP restrictions, changes the gate closure to accept a null user, which forces Laravel not to require authentication.
    Where to look, or what to do
    composer.json, app/Providers/HorizonServiceProvider.php, and any web server or firewall rule in front of /horizon.
    What to write down
    Installed or not; the gate's rule in words; whether the closure accepts a null user and, if it does, what restriction replaced the login and who maintains it.
  8. 8. Debugbar
    What the documentation says
    Debugbar readme (fruitcake/laravel-debugbar, formerly barryvdh/laravel-debugbar): use only in development and not on publicly accessible websites, as it will leak information from stored requests by design. Enabled when APP_DEBUG is true and the environment is not production or testing. DEBUGBAR_FORCE_ALLOW_ENABLE does not enable it but runs its service provider bootstrap so it can be enabled in production; the stored request history answers only localhost or a private network unless DEBUGBAR_OPEN_STORAGE changes that.
    Where to look, or what to do
    composer.json and composer.lock (require or require-dev), config/debugbar.php if it has been published, and the DEBUGBAR_ENABLED, DEBUGBAR_FORCE_ALLOW_ENABLE and DEBUGBAR_OPEN_STORAGE variables in each environment.
    What to write down
    Package name, version and composer.json section, and the value of each of the three variables for each environment, or "not set".
  9. 9. Signed URLs
    What the documentation says
    URL generation page: a signature covers only the path and query string; any other request input, such as a form or JSON body, is not signed, and input read with any method other than query may return unsigned values that override signed ones. Ignored parameters can be changed by anyone. The signed middleware returns 403 for an invalid signature. GHSA-crmm-hgp2-wgrp, GHSA-v5ch-g375-82r6 and GHSA-6rv8-qj5v-p8ch concern temporary signed URL expiry.
    Where to look, or what to do
    php artisan route:list -v for routes carrying the signed middleware, and a code search for signedRoute, temporarySignedRoute, hasValidSignature, hasValidSignatureWhileIgnoring and temporaryUrl.
    What to write down
    Each signed route, what it lets the holder do, its expiry, whether the handler reads signed values with the query method, any ignored parameters, whether request-derived arrays reach signed URL generation, and your framework version against each advisory's patched versions.
  10. 10. Storage disks and visibility
    What the documentation says
    File storage page: disks are set in config/filesystems.php. The local disk's root defaults to storage/app/private. The public disk is intended for publicly accessible files; by default it uses the local driver and stores them in storage/app/public, and storage:link creates the public/storage link that makes them reachable from the web. On the local driver, public visibility translates to 0644 files and 0755 directories, a mapping the filesystems configuration file can change; storePublicly and storePubliclyAs store uploads as public.
    Where to look, or what to do
    config/filesystems.php (each disk's driver, root and visibility, and the links list), and a code search for storePublicly, storePubliclyAs, setVisibility and uses of the public disk.
    What to write down
    Each disk with its driver, root and visibility, and the features that write to it. For each feature that stores customer files: public or private disk, and whether downloads go through a checked route or a temporary URL.
  11. 11. Queue connections and job data
    What the documentation says
    Queues page: connections are set in config/queue.php. Instances of one application sharing a Redis server should each use their own key prefix or Redis database. ShouldBeEncrypted encrypts a job before it is pushed onto the queue. When a job accepts an Eloquent model in its constructor, only the model's identifier is serialised onto the queue. Asynchronous jobs that run out of attempts go to the failed_jobs table, and queue:prune-failed removes records older than 24 hours by default.
    Where to look, or what to do
    config/queue.php and config/database.php (driver, host, prefix and database number, read without the passwords), the network rules around the queue backend, and the job classes.
    What to write down
    The queue driver and backend, what can reach it on the network, which credentials it uses (named, not copied), whether another instance or application shares it and with what prefix, which jobs carry personal or payment details and whether each implements ShouldBeEncrypted, and how long failed job records are kept.
  12. 12. Route and middleware inventory
    What the documentation says
    Routing page: php artisan route:list lists the application's routes; -v adds each route's middleware and middleware group names, -vv expands the groups, and --except-vendor hides routes defined by third-party packages.
    Where to look, or what to do
    Run route:list -v on a copy you control, once as it is and once with --except-vendor.
    What to write down
    For each route that reads or changes customer data: method and URI, whether it is in the web group, and whether it carries auth, can or signed middleware. Package routes such as /telescope and /horizon go on the list too.
  13. 13. Test: mass assignment
    What the documentation says
    Eloquent page: a model needs a Fillable or Guarded attribute before create can be used; attributes outside Fillable are silently discarded by default, and preventSilentlyDiscardingAttributes makes Laravel throw an exception instead; for an unguarded model, the page asks for special care to hand-craft every array passed to fill, create and update.
    Where to look, or what to do
    On staging, signed in as test account A, open the edit form for one of A's own test records. In the browser's element inspector, add a field the form does not send, such as a role flag, an owner or team id, or a status column the model holds, submit, then open the record again.
    What to write down
    The route, the field added, whether the stored record changed, and the model's Fillable or Guarded list. A changed record is the finding; a silently discarded field, or an exception where the application calls preventSilentlyDiscardingAttributes, is the expected result.
  14. 14. Test: CSRF
    What the documentation says
    CSRF page (13.x): the PreventRequestForgery middleware in the web group lets a same-origin request through on the Sec-Fetch-Site header and by default falls back to the token check; in origin-only mode a request that fails origin verification gets a 403 response in place of the 419 typically associated with a token mismatch; Sec-Fetch-Site is sent only over HTTPS; allowSameSite admits same-site requests; the except list excludes URIs; the middleware is switched off automatically when tests run. The 12.x page describes token checks by ValidateCsrfToken and exclusions through validateCsrfTokens.
    Where to look, or what to do
    Read the preventRequestForgery (13.x) or validateCsrfTokens (12.x) call in bootstrap/app.php and list each excluded URI and option. Then, on staging over HTTPS and signed in as test account A, submit a form to one of A's state-changing routes from a page on a different site you control, and open the test record.
    What to write down
    Each excluded URI and what protects it instead, whether allowSameSite or origin-only mode is set, the status code the cross-site submission received, and whether the record changed. A refusal with the record unchanged is the expected result.
  15. 15. Test: object authorisation and roles
    What the documentation says
    Authorisation page: a signed-in user may still not be allowed to update or delete a record. Ways to authorise an action with a policy include the can middleware, the User model's can and cannot methods and the Gate facade; when a gate or policy denies an action a 403 response is returned, and denyAsNotFound returns 404 instead. By default, gates and policies return false for a request from a user who is not signed in. @can in Blade decides what part of a page is displayed.
    Where to look, or what to do
    On staging, test account A creates a record. Signed in as test account B, request A's record by changing its id on each view, edit, update and delete route. Signed in as the lower-role test account, request each administrator route, aimed only at records the test accounts created. Use no other records.
    What to write down
    For each route, method and account: the status code, whether any of A's data appeared, and whether the record changed. A 403 or 404 with nothing changed is the expected result.

What Laravel handles, and what stays with your team

Laravel is a PHP framework.

Its 13.x deployment page says Laravel 13 requires PHP 8.3 or higher, and that the web server should direct all requests to the application's public/index.php file. From that entry point onward, your routes, middleware, controllers, models and views decide what happens to each request.

Some protection is on before anyone writes a line. The 13.x documentation says the CSRF middleware is included in the web middleware group by default, that all Eloquent models are protected against mass assignment by default, and that every value Laravel encrypts is signed with a message authentication code so it cannot be modified once encrypted.

By default, gates and policies return false for a request from a user who is not signed in, unless the user argument is declared optional or given a null default. The Telescope and Horizon dashboards open only in the local environment by default.

What stays with your team is everything those defaults depend on: the values APP_ENV, APP_DEBUG and APP_KEY hold in each environment, which development packages reach the production server, who passes each dashboard gate, which routes sit outside the CSRF middleware, what each controller checks before it reads or changes a record, which files land on a public disk, and who can reach the queue.

The documentation explains what each setting does. Only your application can say what it chose, and that is what the evidence sheet on this page records.

This guide was written from the Laravel 13.x documentation, read on 14 November 2026. Where a feature works differently in the major version you run, follow the documentation for that version. CSRF protection is one example: the 13.x page describes a PreventRequestForgery middleware that checks the browser's Sec-Fetch-Site header before falling back to tokens, while the 12.x page describes a ValidateCsrfToken middleware that compares the token in the request with the one stored in the session.

Laravel versions, support windows and where advisories are published

Laravel's release notes set out its support policy: for all Laravel releases, bug fixes are provided for 18 months and security fixes for 2 years, and a table gives each version its "Security Fixes Until" date.

The same page says Laravel follows Semantic Versioning, with a major release each year and minor and patch releases that may come as often as every week.

Laravel's security policy and its framework advisories are published on the laravel/framework repository on GitHub. Its Security page asks reporters not to disclose security issues publicly and to email the Laravel Security team, refers to the support policy for which versions receive security releases, lists the framework's published advisories and links to the GitHub Advisory Database.

Telescope, Horizon, Debugbar and Ignition are each installed as their own Composer package. Check each one against the advisory database as well.

The advisories this page names are examples that bear on the evidence sheet, read on 14 November 2026. They are not a full list of Laravel vulnerabilities, and the repository's Security page and the GitHub Advisory Database are the places to look for newer entries.

This page's advice is to take the laravel/framework version from the composer.lock of the commit that is deployed, then compare it with the patched versions of each advisory whose affected range includes it.

APP_DEBUG: what Laravel debug mode exposes

The debug option in config/app.php decides how much information about an error is shown to the user, and by default it follows the APP_DEBUG environment variable.

Both the configuration and deployment pages say that in production the value should always be false, and that true in production risks exposing sensitive configuration values to the application's end users. Laravel's configuration files read it as env('APP_DEBUG', false), and the configuration page says the second value is the default, returned if no environment variable exists for the given key.

On that reading, where config/app.php keeps that line, an environment with no APP_DEBUG variable at all falls back to false.

Some published advisories name debug mode as a condition, including the following. GHSA-jh5r-qr3c-85q8 (CVE-2026-102279), published on 10 September 2026, says that when APP_DEBUG=true, attacker-controlled input is passed to a Tippy.js tooltip configured with allowHTML: true, enabling DOM-based XSS during mouse hover. The GitHub Advisory Database lists laravel/framework versions below 12.69.0, and 13.0.0 to before 13.30.0, as affected, with patched versions 12.69.0 and 13.30.0.

The older CVE-2021-3129 (GHSA-4qwp-7c67-jmcc) is in Ignition, a separate package published as facade/ignition. Its record says Ignition before 2.5.2, as used in Laravel and other products, allows unauthenticated remote attackers to execute arbitrary code because of insecure usage of file_get_contents() and file_put_contents(), and that this is exploitable on sites using debug mode with Laravel before 8.4.2.

The database lists facade/ignition versions 2.5.0 to before 2.5.2, 2.0.0 to before 2.4.2, 1.7.0 to before 1.16.14 and below 1.6.15 as affected, with patched versions 2.5.2, 2.4.2, 1.16.14 and 1.6.15.

Because each of these records describes debug mode as a condition, this page asks you to check APP_DEBUG in every environment the internet can reach, staging and preview copies included, and not in production alone, and to note whether Debugbar or Ignition is installed beside it.

One deployment detail changes where you look. The configuration page says config:cache should typically run as part of a production deployment, and that once the configuration has been cached the .env file is not loaded during requests or Artisan commands.

This page's advice follows from that: an APP_DEBUG line in the server's .env file is not proof of what the running application uses, so record where the deployed value is set and read it again after the next deploy.

Laravel APP_KEY: what it protects and what rotating it changes

APP_KEY is the encryption key.

The encryption page says the key option in config/app.php is driven by the APP_KEY environment variable, that php artisan key:generate builds it with PHP's secure random bytes generator, and that it is typically generated for you during installation. Every cookie Laravel sets, session cookies included, is encrypted, and the page says encrypted values are signed so their contents cannot be modified once encrypted.

Rotating the key is a change to the running application, and the documentation says what it changes. If the key changes, all authenticated user sessions are logged out, and data encrypted with the previous key can no longer be decrypted.

APP_PREVIOUS_KEYS takes a comma-delimited list of earlier keys: Laravel encrypts with the current key and, when decrypting, tries the current key first and then each previous key, so users can keep using the application through a rotation.

The sheet on this page does not rotate the key and does not ask you to. If a rotation is needed, plan it with whoever owns the application, from the encryption page.

Where the key lives matters as much as what it is. The configuration page says the .env file should not be committed to source control, since each developer or server may need a different configuration and committing it would be a security risk if an intruder gained access to the repository, because any sensitive credentials would be exposed.

It adds that an encrypted .env.encrypted file may be committed instead, with its decryption key kept in a secure password manager.

The deployment page adds a web server rule: send every request to public/index.php, because serving the application from the project root will expose many sensitive configuration files to the public internet.

On the sheet, note whether APP_KEY has a value, which store holds it and which people or systems have read access to that store. Do not copy it, APP_PREVIOUS_KEYS or LARAVEL_ENV_ENCRYPTION_KEY into the sheet or any other document. If you find the key somewhere it should not be, such as a repository, a ticket or a chat message, start with the secrets exposure guide in this library.

Telescope, Horizon and Debugbar on a live server

Telescope, Horizon and Debugbar each give developers a view inside the running application.

Each documents who it is meant for, and each one's default depends on the environment name the application reports.

Telescope

Laravel describes Telescope as a companion to the local development environment. 1 min read

Horizon

Horizon is a dashboard and configuration system for Redis queues, served at /horizon. 1 min read

Debugbar

Debugbar is a third-party package, published as fruitcake/laravel-debugbar; its readme says the package name changed from barryvdh/laravel-debugbar. 1 min read

Why APP_ENV belongs on the sheet

Telescope and Horizon apply their gates only outside the local environment, Telescope's own page ties public exposure to the APP_ENV value, and Debugbar checks the environment name too. 1 min read

Signed URLs: what the signature covers

Laravel can sign a URL to a named route, appending a signature to the query string so the framework can tell whether the URL was modified after it was created.

The URL generation page suggests them for routes that are publicly accessible but need protection against URL manipulation, such as an unsubscribe link in an email, and temporarySignedRoute adds an expiry that Laravel checks during validation. A route checks the signature with the hasValidSignature method or the signed middleware, which returns a 403 response when the signature is not valid.

The same page is precise about the limit. A signature covers only the URL's path and query string. Any other request input, such as a form or JSON body, is not signed and can be freely modified, and because Laravel gives the request body precedence over the query string, reading a value with any method other than query, such as input, all or a dynamic property, may return an unsigned value in place of the signed one.

Its instruction is to read signed values with the query method, and it notes that this applies to GET requests too, since a specially crafted GET request can still carry a JSON body. Parameters passed to hasValidSignatureWhileIgnoring can be changed by anyone.

Framework advisories also concern the expiry of temporary signed URLs, including the following. GHSA-crmm-hgp2-wgrp says a vulnerability in Laravel's local filesystem driver allows temporary signed URLs to be parsed ambiguously, potentially misrouting requests and bypassing expiration enforcement. Its impact list says expired temporary URLs may continue to be accepted, requests may resolve to a different resource than the one that was signed, and the upload variant may allow writes to reach an unintended destination.

The Advisory Database lists 13.0.0 to before 13.12.0 and versions below 12.61.1 as affected, with patched versions 13.12.0 and 12.61.1, and the repository's own advisory gives it CVE-2026-48041 where the database entry shows no known CVE.

GHSA-v5ch-g375-82r6 says that when PHP's max_input_vars limit drops the expires parameter from the parsed query, an expired temporary signed URL may be accepted, and that exploitation requires a request line long enough to exceed max_input_vars, which depends on server and proxy limits.

GHSA-6rv8-qj5v-p8ch says that when an application passes attacker-influenced, numeric-keyed parameters that do not fill a route placeholder into signedRoute() or temporarySignedRoute(), an attacker can add a second expires field and the signed URL is treated as never expiring. The repository's advisory pages for GHSA-v5ch-g375-82r6 and GHSA-6rv8-qj5v-p8ch each list versions below 12.72.0, and 13.0.0 to before 13.41.0, as affected, and say the issue has been patched in Laravel 12.72.0 and 13.41.0.

The workaround GHSA-6rv8-qj5v-p8ch gives is not to pass request-derived arrays to signed route generation, and to pass only explicitly selected, string-keyed parameters.

This page treats a signed URL as a key that works for whoever holds the link until it expires, unless the route also requires a login. The sheet records, for each signed route, what the link lets its holder do, how long it lasts and how the handler reads its values.

File storage visibility and queue access

Uploaded files and queued jobs both leave the request that created them and wait somewhere else.

Each place has its own idea of who may read it.

Storage disks and visibility

Storage is configured as disks in config/filesystems.php. By default the local disk's root is storage/app/private. The public disk is the one the file storage page describes as intended for files that are going to be publicly accessible: by default it uses the local driver and stores them in storage/app/public, and storage:link creates the public/storage link that makes them reachable from the web.

Visibility is Laravel's abstraction of file permissions. A file declared public should generally be accessible to others, and on the local driver public visibility translates to 0644 for files and 0755 for directories, a mapping the filesystems configuration file can change. storePublicly and storePubliclyAs store an upload with public visibility.

The question for the sheet is where each feature puts what it stores. This page's advice is that invoices, identity documents and anything else tied to one customer belong on a private disk, served through a route that checks who is asking or, where a link is needed, through a temporary URL.

The storage page says temporaryUrl creates temporary URLs to files stored with the local and s3 drivers. GHSA-crmm-hgp2-wgrp concerns temporary signed URLs from the local filesystem driver, so this page applies the version check in the signed URL row here too.

A feature that writes such files to the public disk, or stores them with public visibility, goes on the sheet as a finding to raise with your developers.

Who can reach the queue

config/queue.php decides where jobs wait. Among the drivers included with the framework are database, Amazon SQS, Redis and Beanstalkd. The queues page says the following about access. Where several instances of your application share one Redis server, each instance should use its own key prefix or Redis database, otherwise the queue worker of one instance may process jobs dispatched by another.

A job class that implements ShouldBeEncrypted is encrypted before it is pushed onto the queue, which the page offers for the privacy and integrity of the job's data. When a job accepts an Eloquent model in its constructor, only the model's identifier is serialised onto the queue, and the full model is retrieved again from the database when the job is handled.

An asynchronous job that runs out of attempts is written to the failed_jobs table, and queue:prune-failed removes records older than 24 hours by default.

Horizon is a window onto the same Redis queues, so its gate belongs to the same question. For the sheet, record what can reach the queue backend over the network, which credentials it uses, by name and never by value, whether another instance or application shares it, which jobs carry personal or payment details and whether those jobs are encrypted, and how long failed jobs are kept.

Route and role tests on your own application

The last rows of the sheet are tests, not readings.

They belong only on an application you own, on a staging copy you control that is built from the same commit and configuration as production, with two test accounts in the same role (A and B) and, where your application has roles, one lower-role test account. Use only records those accounts create. Nothing in these tests touches a real person's account or a record that existed before the test.

Start with the route list. The routing page documents php artisan route:list, with -v to show each route's middleware and middleware groups and --except-vendor to hide the routes that packages define. Mark every route that reads or changes customer data with whether it sits in the web group and whether it carries auth, can or signed middleware. Those marks show which routes the tests below need to reach.

Mass assignment

The Eloquent documentation asks for a Fillable or Guarded attribute on a model before create can be used, and says attributes outside Fillable are silently discarded by default, which it calls expected behaviour in production.

It adds that invoking preventSilentlyDiscardingAttributes makes Laravel throw an exception when an unfillable attribute is filled. Where the application does that, expect an error in place of a quiet discard. The test sends a field the form never offers, such as a role flag or an owner id, and then reads the record back. The mass assignment guide in this library covers the mechanism and the fixes in depth.

CSRF

In 13.x the request forgery middleware lets a same-origin request through on the Sec-Fetch-Site header alone, and by default checks the token only when that check does not pass. The page adds details that decide what your test means. Browsers send the Sec-Fetch-Site header only over HTTPS connections, and without HTTPS the middleware falls back to the token check.

Test on a staging copy served over HTTPS. The allowSameSite option admits same-site requests as well as same-origin ones, which the documentation offers for an application that accepts requests from its subdomains; the CSRF guide in this library explains why same site and same origin differ.

And the middleware is switched off automatically for all routes when tests run. For that reason this page does not count a passing test suite as evidence about it.

The browser test submits a form to one of test account A's state-changing routes from a page on a different site you control, and the sheet records what came back and whether the record changed.

Object authorisation

Laravel's authorisation page starts from the point that matters: a signed-in user may still not be allowed to update or delete a given record. Policies group that logic around a particular model or resource. The ways the documentation shows to authorise an action with a policy include the can middleware on a route, the User model's can and cannot methods, and the Gate facade in a controller.

The @can Blade directive decides which portion of a page is displayed. Hiding a button with it does not stop a request to the route behind the button, which needs its own check.

The page says that when a gate or policy denies an action a 403 response is returned, and that denyAsNotFound returns 404 instead. The test has test account B request test account A's record by changing its id on each view, edit, update and delete route, and has the lower-role account request each administrator route, aimed only at records the test accounts created. The broken access control guide in this library sets out the full two-account matrix.

How to fill in the evidence sheet

The sheet is a working record for the person who looks after the application, or for whoever they hand it to.

Paste the table into a spreadsheet and save a separate workbook for each environment.

  • Fill in a copy for every environment the internet can reach: production, staging and any preview or demo copy. A setting that is right in production and wrong on a forgotten staging site still answers requests.
  • Write down what you read, the date and who read it. Where a value can come from more than one place, as when a server-level APP_ENV variable overrides the .env file, record the place the running application uses.
  • Record secrets by fact, never by value: set or not set, where stored, who can read it. That applies to APP_KEY, APP_PREVIOUS_KEYS, LARAVEL_ENV_ENCRYPTION_KEY and every database, Redis and mail credential.
  • Run Artisan commands such as route:list and about on a copy you control, and paste only the lines a row asks for, not the full output.
  • Change nothing while filling it in. A row that shows a setting you want changed becomes a task for whoever owns the deployment, made through your normal release process and then read again.
  • Fill it in again after a framework upgrade, a new package, or a deploy that changes environment variables.

What an owner's review cannot show

The sheet records the settings you read and the routes you tested, on the dates you tested them.

Its limits are worth stating plainly.

  • It covers the routes on your list. A route nobody listed, or code reached another way, such as a queued job, a scheduled task, an Artisan command or a webhook, is outside it.
  • Reading a gate or policy tells you what it allows. It does not show that every route asks it, which is why the tests send requests.
  • Comparing versions with advisories covers published flaws in Laravel and its packages. Your own code has no advisories.
  • A staging result describes staging. Production can differ in environment variables, installed packages and the web server in front.
  • It cannot tell you whether the application has already been misused, for example while debug mode was on in production or a key sat in a repository. Answering that belongs to incident response, and an incident response specialist is the first call.
  • Raw SQL, file uploads, server-side request forgery and other weaknesses have their own guides in this library, and a configuration sheet does not test for them.

Laravel applications and Clever Ops

Laravel applications sit outside the web security services Clever Ops offers.

Clever Ops does not offer a Laravel audit, a Laravel penetration test or a code review of a Laravel application, and nothing on this page describes one. This guide is informational: the evidence sheet is written for your own developers, or for a provider who does test Laravel applications, to work from.

The CSRF, mass assignment, security misconfiguration and secrets exposure guides in this library go further into each of those subjects, and they apply to a Laravel application as they do to any web application.

Frequently asked questions

Laravel's configuration and deployment pages say the value should always be false in production, and that true risks exposing sensitive configuration values to the application's end users. Published advisories also name debug mode as a condition, among them GHSA-jh5r-qr3c-85q8, titled XSS in Debug Page Information, which applies when APP_DEBUG=true, and CVE-2021-3129 in the Ignition package, which its record says is exploitable on sites using debug mode with Laravel before 8.4.2. Check every environment the internet can reach, staging included.

It is the key behind Laravel's encryption services, set through the APP_KEY environment variable and generated with php artisan key:generate. Every cookie Laravel sets, session cookies included, is encrypted. The encryption page says that changing the key logs out all authenticated user sessions and leaves data encrypted with the old key undecryptable, and it offers APP_PREVIOUS_KEYS to mitigate this: Laravel tries each listed earlier key when the current one cannot decrypt a value. On the evidence sheet, note which store holds the key and who has read access to it, and leave the value out.

Telescope's documentation describes it as a companion to local development and documents a local-only installation. Its dashboard opens only in the local environment by default, and the page warns that unless APP_ENV is changed to production in the production environment, the installation will be publicly available. The Debugbar readme says to use it only in development and not on publicly accessible websites, and recommends not installing it in production at all.

For routes in the web middleware group, yes. In 13.x the PreventRequestForgery middleware checks the Sec-Fetch-Site header and falls back to a token check; in 12.x the ValidateCsrfToken middleware compares the token in the request with the one in the session. Routes outside the web group and URIs on the except list are not covered by it, and the 13.x page points an SPA that uses Laravel as an API backend to the Sanctum documentation.

The URL generation page says the signature covers the path and query string and lets Laravel verify that the URL has not been modified since it was created, checked with hasValidSignature or the signed middleware. Anything else in the request, such as a form or JSON body, is not signed, and the URL generation page says to read signed values with the query method so an unsigned body value cannot override them. Query parameters passed to hasValidSignatureWhileIgnoring can be changed by anyone.

Laravel's support policy gives every release bug fixes for 18 months and security fixes for 2 years, and the release notes table lists each version's "Security Fixes Until" date. Published advisories for the framework appear on the Security page of the laravel/framework repository on GitHub and in the GitHub Advisory Database. Check packages such as Telescope, Horizon and Debugbar against the GitHub Advisory Database as well.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.