CVE-2026-41130: Craft CMS has a host header injection leading to SSRF via resource-js endpoint
Summary
The resource-js endpoint in Craft CMS allows unauthenticated requests to proxy remote JavaScript resources. When trustedHosts is not explicitly restricted (default configuration), the application trusts the client-supplied Host header.
This allows an attacker to control the derived baseUrl, which is used in prefix validation inside actionResourceJs(). By supplying a malicious Host header, the attacker can make the server issue arbitrary HTTP requests, leading to Server-Side Request Forgery (SSRF).
Details
The vulnerability exists in AppController::actionResourceJs().
The function validates that the url parameter starts with assetManager->baseUrl. However, baseUrl is derived from the current request host. If trustedHosts is not configured, the Host header is fully attacker-controlled.
Attack chain:
1. Attacker sends request with controlled Host header. 2. Application derives baseUrl from the malicious Host. 3. url parameter is required to start with this baseUrl. 4. Validation passes. 5. Guzzle performs a server-side HTTP request to the attacker-controlled host. 6. SSRF occurs.
This does not rely on string parsing bypass. It relies on Host header trust.
PoC (safe reproduction steps)
Environment: - Craft CMS 5.9.12 - Default configuration (no trustedHosts restriction) - Docker deployment
1. Start a listener inside the container: python3 -m http.server 9999
2. Send a request to resource-js with a controlled Host header.
3. Observe that the internal listener receives a request (OOB confirmation).
Other sources
Craft CMS has a host header injection leading to SSRF via resource-js endpoint
— Packagist
Craft CMS is a content management system (CMS). In versions on the 4.x branch through 4.17.8 and the 5.x branch through 5.9.14, the resource-js endpoint in Craft CMS allows unauthenticated requests to proxy remote JavaScript resources. When trustedHosts is not explicitly restricted (default configuration), the application trusts the client-supplied Host header. This allows an attacker to control the derived baseUrl, which is used in prefix validation inside actionResourceJs(). By supplying a malicious Host header, the attacker can make the server issue arbitrary HTTP requests, leading to Server-Side Request Forgery (SSRF). Versions 4.17.9 and 5.9.15 patch the issue.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/craftcms/cmsto a version that resolves this vulnerability.Fixed in 4.17.9 - Upgrade
Upgrade
composer/craftcms/cmsto a version that resolves this vulnerability.Fixed in 5.9.15 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.17.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.9.15 - Configuration
Configure trustedHosts to explicitly restrict accepted Host header values instead of trusting the client-supplied Host header.
Craft CMS trustedHosts = restricted
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41130?
CVE-2026-41130 is classified as a high severity vulnerability due to its potential for SSRF exploitation.
How do I fix CVE-2026-41130?
To fix CVE-2026-41130, upgrade your Craft CMS to version 4.17.9 or 5.9.15 or later.
Which versions of Craft CMS are affected by CVE-2026-41130?
CVE-2026-41130 affects Craft CMS versions 4.x through 4.17.8 and 5.x through 5.9.14.
What type of vulnerability is CVE-2026-41130?
CVE-2026-41130 is a host header injection vulnerability that leads to server-side request forgery (SSRF).
Can unauthenticated users exploit CVE-2026-41130?
Yes, CVE-2026-41130 can be exploited by unauthenticated users through the vulnerable `resource-js` endpoint.