Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-54182 – Pre-Auth OS Command Injection – Laravel Backpack CRUD (< 4.1.72, 5.x < 5.6.2, 6.x <

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-54182 is a pre-authentication OS command injection vulnerability in the Laravel-Backpack CRUD package, affecting the Stats::makeCurlRequest function used to report usage statistics. The function builds a shell command from the HTTP Host header without adequate sanitization and passes it to exec(), allowing an unauthenticated remote attacker to execute arbitrary operating system commands on the server. The vulnerability carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: BackpackCRUDStats::makeCurlRequest (in src/Stats.php) constructs a shell command using unescaped, attacker-controlled input derived from the HTTP Host header, then executes it via PHP’s exec().
  • Trigger conditions: The vulnerable code path is reached from BackpackServiceProvider::boot() on every HTTP request in production environments where exec() and curl are available on the server. A built-in 1-in-100 random gate limits how often the code path fires, but an attacker can simply retry requests to reliably trigger it.
  • Attack vector: Network, no authentication or user interaction required — an attacker only needs to send an HTTP request with a malicious Host header value.
  • Impact: Successful exploitation results in arbitrary OS command execution with the privileges of the web server process, exposing environment secrets, database credentials, API keys, and filesystem contents, and potentially allowing further data modification or service disruption.

Affected software

  • Laravel-Backpack CRUD 4.1.x: versions before 4.1.72
  • Laravel-Backpack CRUD 5.x: versions 5.0.0 up to before 5.6.2
  • Laravel-Backpack CRUD 6.x: versions 6.0.0 up to before 6.8.13
  • Laravel-Backpack CRUD 7.x: versions 7.0.0 up to before 7.0.36

Severity

CVSS v3.1 Base Score: 8.1 (High)
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Laravel-Backpack CRUD to version 4.1.72, 5.6.2, 6.8.13, or 7.0.36 (or later), depending on the branch in use. The fix replaces the vulnerable shell-based exec()/curl approach with Guzzle-based HTTP requests.
  • If immediate patching is not possible: Validate and restrict the HTTP Host header at the reverse proxy or load balancer level (e.g., allow-list expected hostnames and reject requests with unexpected or malformed Host values) to reduce exposure until the upgrade can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge