hunt-laravel

Identifies high-impact security vulnerabilities in Laravel PHP applications.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill hunt-laravel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-laravel
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/hunt-laravel
Command: npx skills add https://github.com/uphiago/recon-skills --skill hunt-laravel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel applications frequently contain high-impact, framework-specific vulnerabilities that are often missed during standard security assessments, leading to unpatched risks like remote code execution, account takeover, and sensitive credential theft.

Core Features & Use Cases

  • Laravel Fingerprinting: Confirm if a target runs Laravel via session cookies, error pages, and common framework paths.
  • Critical Vulnerability Checks: Test for Ignition RCE (CVE-2021-3129), unauthorized Telescope/Horizon dashboard access, .env exposure with APP_KEY leakage, signed URL bypasses, Eloquent mass assignment, and cookie deserialization.
  • Use Case: During a penetration test of a PHP web application suspected to use Laravel, use this skill to systematically validate all common Laravel misconfigurations and flaws to identify critical, high-severity findings.

Quick Start

Use the hunt-laravel skill to scan the target domain your-target.com for all common Laravel-specific vulnerabilities including debug mode leakage, dashboard exposure, and mass assignment flaws.

Frequently Asked Questions about hunt-laravel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for Laravel security vulnerabilities during a penetration test?

To test for Laravel security vulnerabilities, you systematically validate framework-specific flaws like debug mode exposure, .env APP_KEY leakage, and mass assignment. This process confirms high-impact misconfigurations unique to Laravel applications during authorized security assessments.

What common vulnerabilities affect Laravel applications?

Common Laravel vulnerabilities include Ignition RCE (CVE-2021-3129), unauthorized Telescope or Horizon dashboard access, signed URL bypasses, and Eloquent mass assignment. These framework-specific flaws can lead to remote code execution and account takeover if left unpatched.

How do I find out if a web application uses Laravel?

You can fingerprint a Laravel application by checking for specific session cookies, analyzing framework-specific error pages, and probing common paths. Confirming the target runs Laravel is the first step before testing for its unique security misconfigurations.

Can I detect mass assignment and cookie deserialization flaws in Laravel?

Yes, you can detect Eloquent mass assignment and cookie deserialization flaws by systematically validating common Laravel misconfigurations. Testing these specific vulnerabilities helps identify high-severity findings like account takeover during offensive security engagements.

Does Laravel penetration testing cover APP_KEY leakage and debug mode exposure?

Yes, Laravel penetration testing explicitly covers .env exposure with APP_KEY leakage and debug mode exposure. Validating these specific framework misconfigurations helps uncover critical risks like sensitive credential theft and remote code execution.

What is the best way to check for CVE-2021-3129 Ignition RCE in Laravel?

The best way to check for CVE-2021-3129 Ignition RCE is to systematically test the target application for this specific vulnerability alongside other critical Laravel flaws. This confirms if the framework version is exposed to known remote code execution vectors.