Contao: Server-Side Request Forgery (SSRF) via Unvalidated RSS Feed URL in Feed Reader Module
contao
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| contao/contao Packagist |
|
|
| contao/core-bundle Packagist |
|
contao
| Product | Affected | Fixed in |
|---|---|---|
| contao/contao Packagist |
|
|
| contao/core-bundle Packagist |
|
|
Contao is an Open Source CMS. From 5.3.35 through 5.3.47 and from 5.7.0-RC1 through 5.7.8, the Feed Reader front-end module passes configured RSS feed URLs from FeedReaderController::getResponse() to feedIo->read() without scheme or private-address validation, allowing a backend user with module-edit permissions to make the server request internal network services, loopback addresses, or cloud metadata endpoints. In core-bundle/src/Controller/FrontendModule/FeedReaderController.php, the getResponse() function iterates over the configured feed URLs and passes each one directly to the HTTP client (via $this->feedIo->read($url, new Feed())) with no validation, while the DCA field definition for rss_feed in tl_module.php carries no URL scheme or host validation and the HTTP client is wired as @psr18.http_client (Symfony HttpClient) with no SSRF protection configured, since NoPrivateNetworkHttpClient is not used. This issue is fixed in versions 5.3.48.
From the CVE record · GitHub_M
The Contao Feed Reader front-end module does not validate configured RSS feed URLs before requesting them. A backend user with module-edit permissions can configure a URL that makes the server request internal network services, loopback addresses, or cloud metadata endpoints.
Teams running contao/contao or contao/core-bundle versions >=5.3.35 <5.3.48 or >=5.4.0 <5.7.9 should check their installations.