<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 17:26:09 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-107843</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-107843</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-107843</guid>
    </item>
    <item>
      <title>GHSA-mfxh-vp55-7gc6 — Contao: The registration module re-sends activation mails</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mfxh-vp55-7gc6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: contao/core-bundle&lt;/p&gt;
&lt;p&gt;`ModuleRegistration::compile()` reaches its follow-up registration branch on **any** POST to a page carrying the module. That branch checks neither `FORM_SUBMIT` nor the captcha result computed immediately above it, and `resendActivationMail()` leads to `OptInToken::send()`, which has no rate limit at all.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Anyone on the internet can make a Contao installation send unlimited mail to an address of their choosing, from the site&amp;#39;s own sender and reputation, at one outbound message per HTTP request. That is both a nuisance for the recipient and a deliverability risk for the site operator. The same request is a reliable account oracle for &amp;#34;this address has a pending registration on this site&amp;#34;, which is exactly the sort of membership fact a public site is usually expected not to disclose.&lt;/p&gt;
&lt;p&gt;**Honest bound.** The target must have an unconfirmed registration, that is `tl_member.disable = 1` together with an unconfirmed `reg-` opt-in token. An attacker can create that state for an arbitrary address, since registration requires no ownership proof, but on a site where `reg_activate` is off the branch is unreachable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: contao/core-bundle&lt;/p&gt;
&lt;p&gt;`ModuleRegistration::compile()` reaches its follow-up registration branch on **any** POST to a page carrying the module. That branch checks neither `FORM_SUBMIT` nor the captcha result computed immediately above it, and `resendActivationMail()` leads to `OptInToken::send()`, which has no rate limit at all.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Anyone on the internet can make a Contao installation send unlimited mail to an address of their choosing, from the site&amp;#39;s own sender and reputation, at one outbound message per HTTP request. That is both a nuisance for the recipient and a deliverability risk for the site operator. The same request is a reliable account oracle for &amp;#34;this address has a pending registration on this site&amp;#34;, which is exactly the sort of membership fact a public site is usually expected not to disclose.&lt;/p&gt;
&lt;p&gt;**Honest bound.** The target must have an unconfirmed registration, that is `tl_member.disable = 1` together with an unconfirmed `reg-` opt-in token. An attacker can create that state for an arbitrary address, since registration requires no ownership proof, but on a site where `reg_activate` is off the branch is unreachable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mfxh-vp55-7gc6</guid>
    </item>
  </channel>
</rss>
