CVE-2026-54182
HIGHCVE-2026-54182 is a high-severity (CVSS 8.1) vulnerability in backpack/crud. O3 Security confirms whether CVE-2026-54182 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Laravel Backpack CRUD: OS command injection in Stats::makeCurlRequest via attacker-controlled Host header (pre-auth)
Real-World Exposure
backpack/crud🐘backpack/crud🐘backpack/crud🐘backpack/crudReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Backpack\CRUD\Stats::makeCurlRequest builds a shell command using unescaped input that originates from the HTTP Host header, then passes it to exec(). A specially crafted Host header can break out of the shell argument and cause the server to execute arbitrary OS commands as the web user.
The vulnerable code path is reached from BackpackServiceProvider::boot() on every HTTP request in production when exec() and curl are available. A 1-in-100 random gate is the only guard — an attacker can reliably trigger it by retrying.
Severity
High — CVSS 8.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Complexity is rated High because default nginx and Apache configurations typically strip or reject malformed Host headers before they reach PHP, and exec() is often disabled for web processes in hardened environments. Both mitigations must be absent for exploitation.
Impact
A successful exploit yields OS command execution as the web server user (www-data, nginx, etc.), giving an unauthenticated attacker access to environment secrets (APP_KEY, database credentials, API keys in .env), the filesystem, and any service the server can reach.
Fix
makeCurlRequest was replaced with the Guzzle-based path already present in the codebase, eliminating the shell-command construction entirely. Upgrade to a patched release immediately.
Affected versions
| Branch | Vulnerable range | First safe version |
|---|---|---|
| 4.1.x | < 4.1.70 | 4.1.70 |
| 5.x | < 5.6.2 | 5.6.2 |
| 6.x | < 6.8.13 | 6.8.13 |
| 7.x | < 7.0.36 | 7.0.36 |
Credits
Reported by Vishal Shukla (@shukla304) via sechub.dev AI Agent.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | backpack/crud | ≥ 4.1.0&&< 4.1.72 | 4.1.72 |
| 🐘Packagist | backpack/crud | ≥ 5.0.0&&< 5.6.2 | 5.6.2 |
| 🐘Packagist | backpack/crud | ≥ 6.0.0&&< 6.8.13 | 6.8.13 |
| 🐘Packagist | backpack/crud | ≥ 7.0.0&&< 7.0.36 | 7.0.36 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backpack/crud. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update backpack/crud to 4.1.72 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54182 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-54182 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-54182. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54182 in your dependencies?
O3 detects CVE-2026-54182 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.