<?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>CVE-2026-45225 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-45225/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 12 May 2026 22:22:11 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-45225/feed.xml" rel="self" type="application/rss+xml"/><item><title>Heym Path Traversal Vulnerability in File Upload Endpoint (CVE-2026-45225)</title><link>https://feed.craftedsignal.io/briefs/2026-05-heym-path-traversal/</link><pubDate>Tue, 12 May 2026 22:22:11 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-heym-path-traversal/</guid><description>Heym before 0.0.21 is vulnerable to path traversal, allowing authenticated users to write attacker-controlled files to arbitrary locations by exploiting the unvalidated filename parameter in the upload_file() handler (CVE-2026-45225).</description><content:encoded><![CDATA[<p>Heym before version 0.0.21 contains a path traversal vulnerability in its file upload endpoint. This flaw allows authenticated users to write malicious files to arbitrary locations on the server. By crafting a filename containing traversal sequences (e.g., ../../), an attacker can bypass intended path restrictions and manipulate files outside of the designated upload directory. This vulnerability affects the <code>upload_file()</code> handler due to insufficient validation of the filename parameter. Successful exploitation could lead to arbitrary file write, read, or even deletion, potentially compromising the entire system.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to the Heym application.</li>
<li>Attacker crafts a malicious filename containing path traversal sequences (e.g., <code>../../../evil.php</code>).</li>
<li>Attacker initiates a file upload request to the <code>upload_file()</code> endpoint, including the crafted filename.</li>
<li>The <code>upload_file()</code> handler receives the request but fails to properly sanitize the filename.</li>
<li>The application writes the uploaded file to a location outside the intended directory, based on the path provided in the crafted filename.</li>
<li>The attacker triggers execution of the uploaded file (e.g. if it&rsquo;s a PHP file).</li>
<li>The attacker achieves arbitrary code execution on the server.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to write, read, or delete files outside the intended storage directory. This can lead to arbitrary code execution, allowing the attacker to gain complete control over the affected system. The CVSS v3.1 base score for this vulnerability is 7.6 (High), indicating a significant risk. The potential impact includes unauthorized access to sensitive data, modification of critical system files, and complete system compromise.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Heym to version 0.0.21 or later to patch CVE-2026-45225.</li>
<li>Implement robust filename validation and sanitization within the <code>upload_file()</code> handler to prevent path traversal attacks.</li>
<li>Deploy the Sigma rule <code>Detect Heym Path Traversal File Upload (CVE-2026-45225)</code> to detect exploitation attempts in web server logs.</li>
<li>Monitor web server logs for HTTP requests to the file upload endpoint containing suspicious filename patterns.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>path-traversal</category><category>file-upload</category><category>CVE-2026-45225</category></item></channel></rss>