<?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>Cockpit CMS — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/cockpit-cms/</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, 29 Apr 2026 20:16:29 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/cockpit-cms/feed.xml" rel="self" type="application/rss+xml"/><item><title>Cockpit CMS Authenticated Remote Code Execution via Code Injection</title><link>https://feed.craftedsignal.io/briefs/2026-04-cockpit-rce/</link><pubDate>Wed, 29 Apr 2026 20:16:29 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-cockpit-rce/</guid><description>Cockpit CMS is vulnerable to authenticated remote code execution via PHP code injection in the /cockpit/collections/save_collection endpoint, enabling attackers with collection management privileges to execute arbitrary commands on the server.</description><content:encoded><![CDATA[<p>Cockpit CMS is vulnerable to remote code execution due to insufficient input validation in the <code>/cockpit/collections/save_collection</code> endpoint. An authenticated attacker with collection management privileges can inject arbitrary PHP code into collection rules parameters. This vulnerability, identified as CVE-2026-34965, allows attackers to inject malicious PHP code through rule parameters. The injected code is then written directly to server-side PHP files and executed via the <code>include()</code> function, leading to arbitrary command execution on the underlying server. This poses a significant risk to organizations using Cockpit CMS, potentially leading to complete system compromise.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to the Cockpit CMS application with valid collection management credentials.</li>
<li>Attacker navigates to the <code>/cockpit/collections/save_collection</code> endpoint.</li>
<li>Attacker crafts a malicious request to the <code>/cockpit/collections/save_collection</code> endpoint containing PHP code within collection rules parameters.</li>
<li>The application saves the attacker-supplied PHP code into a PHP file on the server.</li>
<li>The application uses the <code>include()</code> function to execute the PHP file.</li>
<li>The injected PHP code executes arbitrary commands on the underlying server, granting the attacker control of the system.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to execute arbitrary commands on the underlying server. This can lead to complete system compromise, including data theft, modification, or deletion. Given the high CVSS score (8.8), this vulnerability poses a critical risk, especially for internet-facing Cockpit CMS installations. Organizations in any sector using Cockpit CMS are potentially affected.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the patch or upgrade to a version of Cockpit CMS that addresses CVE-2026-34965 to remediate the vulnerability.</li>
<li>Deploy the Sigma rule <code>Detect Suspicious Cockpit CMS Save Collection Activity</code> to identify potential exploitation attempts in web server logs.</li>
<li>Monitor web server logs for POST requests to <code>/cockpit/collections/save_collection</code> with suspicious characters or PHP code in the request body, as detected by the Sigma rule <code>Detect PHP Code Injection in Cockpit CMS Collections</code>.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>rce</category><category>code-injection</category><category>cockpit-cms</category></item></channel></rss>