Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Laravel Security Hardening Review

    1

    Turn a Laravel codebase into a severity-ranked, exploit-traced security report with Laravel-native fixes your team can ship before release.

    Free

    2 usesSecurity scanned
    Laravel Security Hardening Review

    Laravel Security Hardening Review

    Example session with this skill installed

    We're a week from launching a multi-tenant Laravel 11 SaaS and I need a pre-release security review. The code is in ./api — check routes/api.php, the PostController and BillingController, the User and Invoice models, all form requests, and .env.production. I'm especially worried about the invoice file upload endpoint and the reporting endpoints that take a user-supplied sort column. Give me severity-ranked findings with exact file references and the smallest Laravel-native fix for each, plus a short list of anything that must be fixed before we accept production traffic.

    • Read your context and instructions
    • Compiled the laravel security hardening

    Summary

    Security review of shopfront-api (Laravel 11, multi-tenant): 14 findings across 9 entry points — 2 critical, 4 high. All fixes are Laravel-native and fit in one PR cycle; authorization and upload issues should ship before the next deploy.

    SeverityFindingLocationFix
    CriticalDebug mode + .env web-exposed.env.production, public/APP_DEBUG=false, move env out of docroot
    Highcreate($request->all()) allows role/tenant_id injectionUserController::storeWhitelist via FormRequest::validated()
    HighInvoice lookup by ID without tenant scoping (IDOR)InvoiceController::showInvoice::where('tenant_id', $user->tenant_id)->findOrFail($id)
    HighUser-controlled sort column into orderByRawReportControllermatch() whitelist for sort + direction
    MediumInvoice uploads to public disk with original filenameUploadControllerPrivate disk + Str::uuid() filenames
    MediumNo throttle:api on password resetroutes/auth.phpAdd throttle + single-use tokens

    Next steps

    • Merge PR #482 (critical + high fixes) and re-run this audit pre-release
    • Add policy coverage to Post and Invoice models; enforce in CI
    • Purge PII from queued job payloads; pass model IDs instead
    • Re-audit webhooks and Sanctum token scopes after the next sprint

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Laravel applications often ship with hidden vulnerabilities in trust boundaries, request handling, and authorization. This skill transforms your Laravel codebase into a severity-ranked, exploit-traced security report with framework-native fixes.

    What it does

    • Vulnerability discovery identifies missing authorization checks, object ID enumeration, and mass assignment risks.
    • Input trust analysis reviews form requests, validation rules, and raw SQL interpolation.
    • Auth audit inspects login flows, session safety, and token revocation strategies.
    • Infrastructure hardening checks for .env exposure, debug mode leaks, and CORS misconfigurations.
    • Native remediation provides concise, idiomatic Laravel code fixes for every finding.

    How it works

    1. App Mapping defines the application type and maps all external entry points like routes, webhooks, and queues.
    2. Input Tracing follows untrusted data from query strings or JSON bodies to sensitive sinks like the database or file system.
    3. Severity Ranking categorizes findings from Critical to Informational based on real-world exploitability.
    4. Fix Generation outputs a prioritized remediation report with specific code examples for your team.

    Frameworks & tools

    Laravel 8.x through 11.x, Eloquent ORM, Laravel Sanctum, Blade templating, and PHP 8.x security standards.

    Why this beats prompting it yourself

    Generic security prompts often suggest unnecessary third-party packages or ignore Laravel features like Policy-based authorization and FormRequests. This skill uses the framework's own architecture to secure the app, ensuring fixes are maintainable and idiomatic.

    Use cases

    • Auditing a legacy Laravel app before a major version upgrade.
    • Performing a pre-release security checklist for new API endpoints.
    • Reviewing third-party integrations, webhooks, and queued jobs for data leaks.
    • Training junior developers by showing exploit paths in their PRs.

    Known limitations

    This skill focuses on the Laravel application layer. It does not audit low-level server OS hardening, network firewalls, or third-party PHP packages outside the Laravel ecosystem.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Static review only — it does not execute, fuzz, or penetration-test the running app, so runtime-only and infrastructure issues (server config, vulnerable dependency versions) need separate tooling. Findings quality depends on the agent being able to read the whole codebase; partial file access yields partial coverage.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    2 uses

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Write Files

    File Scopes

    routes/**
    app/**/*.php
    config/**
    database/**
    .env*

    Needs read access to the project's PHP source, routes, and config to trace untrusted inputs to sensitive sinks, with write access only for saving the findings report.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The skill focuses on the application layer, covering Laravel versions 8.x through 11.x and PHP 8.x, including core components like Eloquent, Sanctum, and Blade.

    You will receive a comprehensive, severity-ranked report detailing exploit paths and providing specific, idiomatic Laravel code fixes for every identified vulnerability.

    Unlike generic tools, this skill leverages Laravel-native features like FormRequests and Policies to provide maintainable fixes that align with the framework's architecture rather than suggesting external dependencies.

    The skill maps application entry points and traces input data, but it is limited to the Laravel application layer and does not audit OS-level hardening or network firewall configurations.

    This skill is designed to integrate into your existing workflow, typically requiring access to your codebase or specific route files to begin the mapping and tracing process.

    New in Security

    Free