<?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>Webui — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/webui/</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>Mon, 04 May 2026 21:24:50 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/webui/feed.xml" rel="self" type="application/rss+xml"/><item><title>Pelican Web UI Privilege Escalation Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-pelican-privesc/</link><pubDate>Mon, 04 May 2026 21:24:50 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-pelican-privesc/</guid><description>A privilege escalation vulnerability in Pelican WebUI versions v7.21 to v7.24 allows authenticated users to gain admin privileges by manipulating database records, potentially leading to configuration modification, API token creation, and password changes.</description><content:encoded><![CDATA[<p>On April 2nd, 2026, a privilege escalation vulnerability was identified in the Pelican Web User Interface (WebUI) affecting versions v7.21 to v7.24. This vulnerability allows any authenticated user via OAuth to gain admin privileges under specific configurations, including servers with <code>Server.UIAdminUsers</code> where listed users haven&rsquo;t logged in or <code>Server.AdminGroups</code> with <code>Issuer.GroupSource</code> set to <code>internal</code> where an admin hasn&rsquo;t logged in. Successful exploitation permits attackers to modify server configurations, create API tokens, and change admin passwords. The OSDF operations team mitigated this vulnerability for core services, but mitigation may be required for other caches and origins. There is currently no evidence this attack has been exploited in services managed by OSDF operators.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to the Pelican WebUI by authenticating via OIDC.</li>
<li>The attacker identifies a valid <code>Server.UIAdminUsers</code> username or <code>Server.AdminGroups</code> group name for an admin who has not yet logged into the WebUI.</li>
<li>The attacker crafts malicious database records designed to grant admin privileges upon subsequent login.</li>
<li>The attacker injects these records into the Pelican server&rsquo;s SQLite database, potentially using API endpoints or other methods to interact with the database.</li>
<li>The attacker logs out of the WebUI.</li>
<li>The attacker logs back into the WebUI.</li>
<li>The server grants the attacker admin privileges based on the manipulated database records.</li>
<li>The attacker modifies server configurations, creates persistent API tokens, or changes admin passwords.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The successful exploitation of this vulnerability poses a significant risk to Pelican servers and the wider federation they support. A compromised Director service could have high federation-wide impact, enabling denial of service and redirection to malicious registries. Registry services also have high federation-wide impact, with attackers potentially poisoning namespaces. Compromised Origins could lead to high data exposure and tampering risks by enabling unauthorized writes and changing export paths. Caches present a medium data exposure risk, as attackers could expose cached protected data.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Run the provided mitigation script (<code>mitigate-user-escalation.sh</code> from <a href="https://gist.github.com/jhiemstrawisc/8c4b2b3ec5cb2ca06537d9439dc16cc9">https://gist.github.com/jhiemstrawisc/8c4b2b3ec5cb2ca06537d9439dc16cc9</a>) to audit the database for signs of exploitation and block further exploitation.</li>
<li>Upgrade Pelican servers to a patched release (&gt;=v7.21.5, &gt;=v7.22.3, &gt;=v7.23.3, &gt;=v7.24.2).</li>
<li>If unable to upgrade immediately, disable the vulnerable configuration by commenting out <code>UIAdminUsers</code> and <code>AdminGroups</code> settings in the <code>pelican.yaml</code> configuration file.</li>
<li>Monitor process executions for the <code>mitigate-user-escalation.sh</code> script and review associated user and API token changes. Deploy the provided Sigma rule to detect potential malicious activity.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>privilege-escalation</category><category>webui</category><category>pelican</category></item><item><title>Hermes WebUI Arbitrary File Deletion Vulnerability (CVE-2026-6832)</title><link>https://feed.craftedsignal.io/briefs/2026-04-hermes-file-deletion/</link><pubDate>Wed, 22 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-hermes-file-deletion/</guid><description>Hermes WebUI is vulnerable to arbitrary file deletion via path traversal in the /api/session/delete endpoint due to insufficient validation of the session_id parameter, allowing authenticated attackers to delete writable JSON files on the host system.</description><content:encoded><![CDATA[<p>Hermes WebUI, a web-based user interface, contains an arbitrary file deletion vulnerability, tracked as CVE-2026-6832. The vulnerability resides in the <code>/api/session/delete</code> endpoint. An authenticated attacker can exploit this flaw by supplying a crafted <code>session_id</code> parameter containing an absolute path or path traversal sequences. This allows the attacker to bypass the intended <code>SESSION_DIR</code> boundary and delete arbitrary files on the server, provided the attacker has write access to those files. Versions prior to the patched version are affected. Successful exploitation leads to information integrity issues and potential denial of service.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to Hermes WebUI using valid credentials.</li>
<li>Attacker crafts a malicious HTTP POST request to the <code>/api/session/delete</code> endpoint.</li>
<li>The request includes a <code>session_id</code> parameter with a path traversal payload (e.g., <code>../../../../etc/passwd</code>) or an absolute path to a target file.</li>
<li>The Hermes WebUI application fails to properly validate the <code>session_id</code> parameter.</li>
<li>The application constructs a file path using the unvalidated <code>session_id</code>, allowing it to escape the intended <code>SESSION_DIR</code>.</li>
<li>The application attempts to delete the file specified by the attacker-controlled path.</li>
<li>If the attacker has sufficient privileges, the target file is successfully deleted from the file system.</li>
<li>The deletion of critical system or application files leads to a denial-of-service condition or other system instability.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-6832 allows authenticated attackers to delete arbitrary files on the system running Hermes WebUI. This can lead to data loss, application malfunction, or even complete system compromise if critical system files are deleted. The vulnerability affects all deployments of Hermes WebUI prior to the patched version, potentially impacting numerous organizations using the vulnerable software. While the exact number of victims is unknown, the severity of the vulnerability is high due to the potential for significant damage and disruption.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Hermes WebUI to version v0.50.132 or later, where the vulnerability is patched, as referenced in the advisory.</li>
<li>Implement strict input validation on the <code>session_id</code> parameter in the <code>/api/session/delete</code> endpoint to prevent path traversal attacks.</li>
<li>Deploy the provided Sigma rule to detect malicious requests to the <code>/api/session/delete</code> endpoint containing path traversal sequences.</li>
<li>Monitor web server logs for HTTP requests to <code>/api/session/delete</code> with suspicious <code>session_id</code> values.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-6832</category><category>path-traversal</category><category>file-deletion</category><category>webui</category></item></channel></rss>