Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-57232 low CVSS 3.1

SSRF (Server-Side Request Forgery) in contao/contao (CVE-2026-57232)

Summary

SSRF in contao/contao (CVE-2026-57232). Risk of unauthorized operations or information disclosure. Exploitable via rss_feed. Mitigation: upgrade to 5.7.9 or later.

Original description

The description as published by the source.

Summary

The Feed Reader front-end module passes RSS feed URLs from its configuration directly to $this->feedIo->read($url) without any scheme validation or private-IP blocklist. A backend user with module-edit permissions can configure an arbitrary URL pointing to internal network services, cloud-provider metadata endpoints, or loopback addresses, causing the server to fetch those resources unconditionally. Confirmed live: the server successfully reaches the internal MySQL database container and its own loopback Apache instance.

Details

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 with no validation:

// Line 50-55
foreach (StringUtil::trimsplit('[\n\t ]', trim($model->rss_feed)) as $url) {
    try {
        $feed = $this->cache->get(
            'feed_reader_'.$model->id.'_'.md5($url),
            function (ItemInterface $item) use ($url, $model) {
                $readerResult = $this->feedIo->read($url, new Feed()); // <-- no validation

The DCA field definition for rss_feed in tl_module.php carries no URL scheme or host validation:

'eval' => array('mandatory'=>true, 'decodeEntities'=>true, 'style'=>'height:60px')

The HTTP client is wired as @psr18.http_client (Symfony HttpClient) with no SSRF protection configured (NoPrivateNetworkHttpClient is not used).

Impact

This is a…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-57232 has been found in contao/contao.
Attackers can target a specific entry point like rss_feed over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade contao/contao to 5.7.9 or later.
If unsure, ask your IT team or search "contao/contao CVE-2026-57232" on the vendor's site.

CVE-2026-57232 (contao/contao) — CWE-918 / CVSS v3 3.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: rss_feed / tl_module.php / NoPrivateNetworkHttpClient / tl_module.rss_feed
Patched: 5.7.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in contao/contao. Attackers reach the vulnerable code path via rss_feed.

📍 Affected scope

Check the vendor advisory for the affected versions of contao/contao. Attack surface: rss_feed / tl_module.php / NoPrivateNetworkHttpClient / tl_module.rss_feed.

🔥 Severity

Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.7.9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'contao/contao' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'contao/contao' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で contao/contao を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade contao/contao to 5.7.9

    ステージング環境で 5.7.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer contao/contao
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.7.9"}]}]
composer contao/core-bundle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.7.9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details