ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107848

Contao: Cross-site request forgery in custom backend actions

Published Oct 9, 2026 · catalog updated Oct 9, 2026 · Contao: Cross-site request forgery

Check if you run it

No confirmed exploitation is on record for CVE-2026-107848. EPSS is 0.11%. Act only if a listed version of Contao: Cross-site request forgery is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Contao: Cross-site request forgery).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low3.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.11%
Remediation
Advisory link
Affected products
Packagist contao/core-bundle

is the only generic validator in Contao and it only runs on POST. On the GET side the guard is local and declarative, and it only fires when an parameter is present. Every back end action dispatched through a different parameter therefore has no CSRF protection at all. This is a family rather than a single bug. ### Impact An attacker who gets a logged in back end user to load a URL performs back end actions as that user, with no token and no confirmation. Because the exposure follows from the dispatch mechanism rather than from one callback, every present and future action inherits it. **Honest bound.** The victim must be authenticated in the back end and must load the URL, and the reachable actions are limited to the modules that user can access. We have not found a action that grants privileges; the ones we verified are destructive or state changing rather than escalating.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Packagist contao/core-bundle4.0.0 → 5.3.50
  • Packagist contao/core-bundle5.4.0-RC1 → 5.7.12

How to fix CVE-2026-107848

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107848. EPSS is 0.11%. Act only if a listed version of Contao: Cross-site request forgery is installed.

Which versions are affected?

Compare what you have installed with 4.0.0 → 5.3.50, 5.4.0-RC1 → 5.7.12. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-352: Cross-Site Request Forgery (CSRF). EPSS 0.11%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 9, 2026 · Catalog

    Detected

    is the only generic validator in Contao and it only runs on POST. On the GET side the guard is local and declarative, and it only fires when an parameter is present. Every back end action dispatched through a different parameter therefore has no CSRF protection at all. This is a family rather than a single bug. ### Impact An attacker who gets a logged in back end user to load a URL performs back e

  2. Oct 9, 2026 · Catalog

    Fix available

    Packagist contao/core-bundle 4.0.0 → 5.3.50

  3. Oct 9, 2026 · Catalog

    Fix available

    Packagist contao/core-bundle 5.4.0-RC1 → 5.7.12

  4. Oct 9, 2026 · GitHub Advisory Database

    Fix available

    contao/core-bundle fixed in 5.3.50; contao/core-bundle fixed in 5.7.12

  5. Oct 9, 2026 · GitHub Advisory Database

    Fix available

    contao/core-bundle fixed in 5.3.50

  6. Oct 9, 2026 · GitHub Advisory Database

    Fix available

    contao/core-bundle fixed in 5.7.12

  7. Oct 9, 2026 · Catalog

    Updated

    is the only generic validator in Contao and it only runs on POST. On the GET side the guard is local and declarative, and it only fires when an parameter is present. Every back end action dispatched through a different parameter therefore has no CSRF protection at all. This is a family rather than a single bug. ### Impact An attacker who gets a logged in back end user to load a URL performs back e

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.