<?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>Mon, 12 Oct 2026 08:32:07 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-29069</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-29069</link>
      <description>&lt;p&gt;Craft is a content management system (CMS). Prior to 5.9.0-beta.2 and 4.17.0-beta.2, the actionSendActivationEmail() endpoint is accessible to unauthenticated users and does not require a permission check for pending users. An attacker with no prior access can trigger activation emails for any pending user account by knowing or guessing the user ID. If the attacker controls the target user’s email address, they can activate the account and gain access to the system. This vulnerability is fixed in 5.9.0-beta.2 and 4.17.0-beta.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft is a content management system (CMS). Prior to 5.9.0-beta.2 and 4.17.0-beta.2, the actionSendActivationEmail() endpoint is accessible to unauthenticated users and does not require a permission check for pending users. An attacker with no prior access can trigger activation emails for any pending user account by knowing or guessing the user ID. If the attacker controls the target user’s email address, they can activate the account and gain access to the system. This vulnerability is fixed in 5.9.0-beta.2 and 4.17.0-beta.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-29069</guid>
    </item>
    <item>
      <title>GHSA-234q-vvw3-mrfq — Craft CMS has unauthenticated activation email trigger with potential user enumeration</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-234q-vvw3-mrfq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;The `actionSendActivationEmail()` endpoint is accessible to unauthenticated users and does not require a permission check for pending users. An attacker with no prior access can trigger activation emails for any pending user account by knowing or guessing the user ID. If the attacker controls the target user’s email address, they can activate the account and gain access to the system.&lt;/p&gt;
&lt;p&gt;The vulnerability is not that anonymous access exists - there’s a legitimate use case for it. The vulnerability is that the endpoint accepts arbitrary `userId` parameters without verifying ownership.&lt;/p&gt;
&lt;p&gt;Craft CMS allows public user registration. When a user registers but doesn’t receive their activation email (spam filter, typo correction, etc.), they need a way to request a resend. This is why `send-activation-email` is in the `allowAnonymous` array - it’s intentional self-service functionality.&lt;/p&gt;
&lt;p&gt;### The Security Gap&lt;/p&gt;
&lt;p&gt;The endpoint accepts `userId` as the identifier:
```php
$userId = $this-&amp;gt;request-&amp;gt;getRequiredBodyParam(&amp;#39;userId&amp;#39;);
```&lt;/p&gt;
&lt;p&gt;This allows any visitor to trigger activation emails for any pending user, not just their own registration.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Background&lt;/p&gt;
&lt;p&gt;When administrators create new user accounts in Craft CMS, users are created in a “pending” state until they activate their account via an emailed link. The `actionSendActivationEmail()` function sends (or resends) this activation email.&lt;/p&gt;
&lt;p&gt;**Expected Behavior:** Anonymous users should only be able to resend activation emails for their own…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;The `actionSendActivationEmail()` endpoint is accessible to unauthenticated users and does not require a permission check for pending users. An attacker with no prior access can trigger activation emails for any pending user account by knowing or guessing the user ID. If the attacker controls the target user’s email address, they can activate the account and gain access to the system.&lt;/p&gt;
&lt;p&gt;The vulnerability is not that anonymous access exists - there’s a legitimate use case for it. The vulnerability is that the endpoint accepts arbitrary `userId` parameters without verifying ownership.&lt;/p&gt;
&lt;p&gt;Craft CMS allows public user registration. When a user registers but doesn’t receive their activation email (spam filter, typo correction, etc.), they need a way to request a resend. This is why `send-activation-email` is in the `allowAnonymous` array - it’s intentional self-service functionality.&lt;/p&gt;
&lt;p&gt;### The Security Gap&lt;/p&gt;
&lt;p&gt;The endpoint accepts `userId` as the identifier:
```php
$userId = $this-&amp;gt;request-&amp;gt;getRequiredBodyParam(&amp;#39;userId&amp;#39;);
```&lt;/p&gt;
&lt;p&gt;This allows any visitor to trigger activation emails for any pending user, not just their own registration.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Background&lt;/p&gt;
&lt;p&gt;When administrators create new user accounts in Craft CMS, users are created in a “pending” state until they activate their account via an emailed link. The `actionSendActivationEmail()` function sends (or resends) this activation email.&lt;/p&gt;
&lt;p&gt;**Expected Behavior:** Anonymous users should only be able to resend activation emails for their own…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-234q-vvw3-mrfq</guid>
    </item>
  </channel>
</rss>
