GHSA-mrc5-3mm3-45c5: Input Validation

Published Aug 20, 2026
·
Updated

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 (APPKEY, 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 Software

4 affected componentsFixes available
composer/backpack/crud>=7.0.0<7.0.36
7.0.36
composer/backpack/crud>=6.0.0<6.8.13
6.8.13
composer/backpack/crud>=5.0.0<5.6.2
5.6.2
composer/backpack/crud>=4.1.0<4.1.72
4.1.72

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/backpack/crud to a version that resolves this vulnerability.

    Fixed in 7.0.36
  2. Upgrade

    Upgrade composer/backpack/crud to a version that resolves this vulnerability.

    Fixed in 6.8.13
  3. Upgrade

    Upgrade composer/backpack/crud to a version that resolves this vulnerability.

    Fixed in 5.6.2
  4. Upgrade

    Upgrade composer/backpack/crud to a version that resolves this vulnerability.

    Fixed in 4.1.72
  5. Upgrade

    Upgrade 4.1.x to a version that resolves this vulnerability.

    Fixed in 4.1.70
  6. Upgrade

    Upgrade 5.x to a version that resolves this vulnerability.

    Fixed in 5.6.2
  7. Upgrade

    Upgrade 6.x to a version that resolves this vulnerability.

    Fixed in 6.8.13
  8. Upgrade

    Upgrade 7.x to a version that resolves this vulnerability.

    Fixed in 7.0.36
  9. Compensating control

    Ensure that for the web server process, `exec()` and `curl` are not available/allowed (the vulnerable path is reachable from `BackpackServiceProvider::boot()` and requires `exec()` and `curl`).

  10. Compensating control

    Configure nginx/Apache to strip or reject malformed Host headers so they do not reach the PHP code path (default nginx/Apache configurations typically do this).

Event History

Aug 20, 2026
Advisory Published
via GitHub·06:38 PM
Data Sourced
via GitHub·06:38 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Are typical nginx or Apache deployments affected by default?

Typically, default nginx and Apache configurations strip or reject malformed Host headers before they reach PHP. Exploitation also requires exec() to be enabled for the web process, so both protections must be absent.

2

Does exploitation require authentication or user interaction?

No. An unauthenticated attacker can send a specially crafted Host header, and no user interaction is required. The 1-in-100 random gate can be overcome by retrying requests.

3

What can be done if patching cannot happen immediately?

Ensure the front-end web server rejects malformed Host headers before they reach PHP, and disable exec() for the web process where feasible. Either measure prevents the stated exploitation path.

4

How can I assess whether an installation is exposed?

Check production deployments of composer/backpack/crud for whether curl and exec() are available to the web process and whether the proxy or web server permits malformed Host headers to reach PHP. The vulnerable path is invoked on every HTTP request in production when exec() and curl are available.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203