<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Grav Core — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/grav-core/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 03 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/grav-core/feed.xml" rel="self" type="application/rss+xml"/><item><title>Grav Login Plugin Privilege Escalation Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2024-01-grav-privesc/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-grav-privesc/</guid><description>Unauthenticated users can escalate privileges to admin in Grav CMS by manipulating registration data due to missing server-side validation in the Login plugin.</description><content:encoded><![CDATA[<p>A critical privilege escalation vulnerability exists in the Grav CMS Login plugin, version 3.8.0, affecting Grav Core versions prior to 2.0.0-beta.2. The vulnerability stems from the <code>Login::register()</code> method not validating the <code>groups</code> and <code>access</code> fields during user registration. If registration is enabled and these fields are included in the allowed registration fields, an unauthenticated user can craft a malicious registration request to assign themselves admin privileges. This can lead to complete compromise of the Grav CMS instance, allowing attackers to modify content, install malicious plugins, and potentially execute arbitrary code. The vulnerability is tracked as CVE-2026-42613. The fix was applied on 2026-04-24 and released in grav-plugin-login 3.8.2.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies a Grav CMS instance with user registration enabled and the <code>groups</code> or <code>access</code> fields included in the allowed registration fields.</li>
<li>The attacker crafts a malicious HTTP POST request to the <code>/user_register</code> endpoint, including <code>username</code>, <code>password</code>, <code>email</code>, and <code>fullname</code> fields.</li>
<li>The attacker injects <code>groups</code> and <code>access</code> fields into the POST request with values designed to grant admin privileges (e.g., <code>groups[]=admins</code>, <code>access[admin][super]=true</code>).</li>
<li>The <code>Login::register()</code> method processes the registration data without proper validation of the injected <code>groups</code> and <code>access</code> fields.</li>
<li>The attacker-controlled <code>groups</code> and <code>access</code> values are assigned directly to the newly created user object.</li>
<li>The user object is saved, creating a new user account with admin privileges in the <code>user/accounts/</code> directory.</li>
<li>The attacker logs in to the Grav admin panel using the newly created account.</li>
<li>The attacker leverages their admin access to install malicious plugins or execute arbitrary code on the server, achieving complete system compromise.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability grants unauthenticated attackers full administrative access to the Grav CMS instance. This can lead to complete website defacement, data exfiltration, or remote code execution. Since no victim count or specific sector targeting is mentioned in the advisory, we can assume any Grav instance with the vulnerable configuration is at risk, potentially impacting numerous websites and organizations relying on Grav CMS.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to grav-plugin-login version 3.8.2 or later to patch CVE-2026-42613.</li>
<li>If upgrading is not immediately feasible, remove <code>groups</code> and <code>access</code> from the allowed registration fields in the Login plugin configuration.</li>
<li>Deploy the Sigma rule <code>Detect Malicious Grav User Registration</code> to identify registration attempts with injected admin privileges based on user-registration requests.</li>
<li>Monitor web server logs for POST requests to the <code>/user_register</code> endpoint containing <code>groups</code> or <code>access</code> parameters using the <code>Grav Registration Attempt with Group/Access Parameters</code> Sigma rule.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>grav</category><category>privilege-escalation</category><category>web</category></item></channel></rss>