cve.bz

CVE-2026-107843 contao contao: Observable Response Discrepancy

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in contao contao. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in contao/core-bundle 5.3.50, 5.7.12.

On this page
Contao is an Open Source CMS. From version 4.1.0 until 5.3.50 and 5.7.12, ModuleRegistration::compile() enters its follow-up registration branch on any POST to a page containing the registration module without verifying FORM_SUBMIT or the preceding captcha result. resendActivationMail() can then invoke OptInToken::send() without rate limiting, allowing an unauthenticated attacker to cause repeated activation emails to be sent to an address with a pending registration and to determine whether that pending registration exists. The branch is reachable only when reg_activate is enabled and the target has an unconfirmed registration and opt-in token. This issue is fixed in versions 5.3.50 and 5.7.12.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-204 Observable Response Discrepancy
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • contao/core-bundle (Packagist): fixed in 5.3.50, 5.7.12

Ask an AI about this CVE

Show the promptExplain CVE-2026-107843 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107843?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107843?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107843 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
contao>= 4.1.0, < 5.3.50
contao>= 5.4.0-RC1, < 5.7.12

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mfxh-vp55-7gc6Packagistcontao/core-bundle>=4.1.0 <5.3.505.3.50
GHSA-mfxh-vp55-7gc6Packagistcontao/core-bundle>=5.4.0-RC1 <5.7.125.7.12

Attack patterns (CAPEC)

  • CAPEC-331 ICMP IP Total Length Field Probe Likelihood: Medium · Severity: Low
  • CAPEC-332 ICMP IP 'ID' Field Error Message Probe Likelihood: Medium · Severity: Low
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON