https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 05:05:46 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-100667 <p>grav-plugin-login (the Grav CMS Login plugin) versions &gt;= 3.8.7 and &lt; 3.9.7 allow the two-factor authentication challenge to be bypassed for content gated by the authenticated() Twig function or the [authenticated] shortcode. On sites with 2FA enabled, Login::isAuthenticated() checked only the session flag indicating that the password step had succeeded, not the flag indicating that login had completed, so a session sitting at the 2FA code prompt was treated as fully authenticated. An attacker who knows a member&#39;s password but cannot answer that member&#39;s second factor can therefore read member-only content rendered by the no-argument authenticated() or group authenticated(null, &#39;group&#39;) forms and by [authenticated]; the inverse [guest] shortcode is likewise evaluated too early. Impact is limited to disclosure of that content: the attacker does not obtain a completed session, cannot access pages protected by an access: rule, and cannot act as the user. The authenticated(&#39;some.permission&#39;) form, which goes through UserObject::authorize(), is not affected. Fixed in grav-plugin-login 3.9.7.</p> <p>grav-plugin-login (the Grav CMS Login plugin) versions &gt;= 3.8.7 and &lt; 3.9.7 allow the two-factor authentication challenge to be bypassed for content gated by the authenticated() Twig function or the [authenticated] shortcode. On sites with 2FA enabled, Login::isAuthenticated() checked only the session flag indicating that the password step had succeeded, not the flag indicating that login had completed, so a session sitting at the 2FA code prompt was treated as fully authenticated. An attacker who knows a member&#39;s password but cannot answer that member&#39;s second factor can therefore read member-only content rendered by the no-argument authenticated() or group authenticated(null, &#39;group&#39;) forms and by [authenticated]; the inverse [guest] shortcode is likewise evaluated too early. Impact is limited to disclosure of that content: the attacker does not obtain a completed session, cannot access pages protected by an access: rule, and cannot act as the user. The authenticated(&#39;some.permission&#39;) form, which goes through UserObject::authorize(), is not affected. Fixed in grav-plugin-login 3.9.7.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-100667 https://vulnerability.circl.lu/vuln/ghsa-r29m-xqx4-rwgf <p>grav-plugin-login (the Grav CMS Login plugin) versions &gt;= 3.8.7 and &lt; 3.9.7 allow the two-factor authentication challenge to be bypassed for content gated by the authenticated() Twig function or the [authenticated] shortcode. On sites with 2FA enabled, Login::isAuthenticated() checked only the session flag indicating that the password step had succeeded, not the flag indicating that login had completed, so a session sitting at the 2FA code prompt was treated as fully authenticated. An attacker who knows a member&#39;s password but cannot answer that member&#39;s second factor can therefore read member-only content rendered by the no-argument authenticated() or group authenticated(null, &#39;group&#39;) forms and by [authenticated]; the inverse [guest] shortcode is likewise evaluated too early. Impact is limited to disclosure of that content: the attacker does not obtain a completed session, cannot access pages protected by an access: rule, and cannot act as the user. The authenticated(&#39;some.permission&#39;) form, which goes through UserObject::authorize(), is not affected. Fixed in grav-plugin-login 3.9.7.</p> <p>grav-plugin-login (the Grav CMS Login plugin) versions &gt;= 3.8.7 and &lt; 3.9.7 allow the two-factor authentication challenge to be bypassed for content gated by the authenticated() Twig function or the [authenticated] shortcode. On sites with 2FA enabled, Login::isAuthenticated() checked only the session flag indicating that the password step had succeeded, not the flag indicating that login had completed, so a session sitting at the 2FA code prompt was treated as fully authenticated. An attacker who knows a member&#39;s password but cannot answer that member&#39;s second factor can therefore read member-only content rendered by the no-argument authenticated() or group authenticated(null, &#39;group&#39;) forms and by [authenticated]; the inverse [guest] shortcode is likewise evaluated too early. Impact is limited to disclosure of that content: the attacker does not obtain a completed session, cannot access pages protected by an access: rule, and cannot act as the user. The authenticated(&#39;some.permission&#39;) form, which goes through UserObject::authorize(), is not affected. Fixed in grav-plugin-login 3.9.7.</p> https://vulnerability.circl.lu/vuln/ghsa-r29m-xqx4-rwgf