<?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>Arbitrary-File-Upload — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/arbitrary-file-upload/</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>Sat, 02 May 2026 10:16:18 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/arbitrary-file-upload/feed.xml" rel="self" type="application/rss+xml"/><item><title>Sunnet CTMS/CPAS Arbitrary File Upload Vulnerability (CVE-2026-7490)</title><link>https://feed.craftedsignal.io/briefs/2026-05-sunnet-file-upload/</link><pubDate>Sat, 02 May 2026 10:16:18 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-sunnet-file-upload/</guid><description>A privileged remote attacker can exploit CVE-2026-7490 in Sunnet CTMS and CPAS to upload and execute web shell backdoors, leading to arbitrary code execution on the server.</description><content:encoded><![CDATA[<p>CVE-2026-7490 is an arbitrary file upload vulnerability found in Sunnet CTMS and CPAS. Disclosed in May 2026, this vulnerability enables a privileged attacker to upload malicious files, specifically web shell backdoors, to the affected server. This can be achieved remotely, without requiring local system access, given the attacker already possesses valid privileged credentials for the application. Successful exploitation allows the attacker to execute arbitrary code on the server, potentially leading to complete system compromise. This vulnerability poses a significant threat to organizations using these Sunnet products, as it could result in data breaches, service disruption, and other malicious activities.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains privileged access to the CTMS or CPAS application, either through credential theft, phishing, or other means.</li>
<li>Attacker identifies the file upload functionality within the application.</li>
<li>Attacker crafts a malicious file, such as a PHP web shell, designed to execute arbitrary commands on the server.</li>
<li>Attacker bypasses any client-side file type validation mechanisms.</li>
<li>Attacker uploads the malicious file to the server through the vulnerable file upload endpoint.</li>
<li>The application saves the file to a publicly accessible directory without proper sanitization or validation.</li>
<li>Attacker accesses the uploaded web shell via a web browser.</li>
<li>Attacker uses the web shell to execute arbitrary commands on the server, leading to full system compromise.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-7490 allows attackers to execute arbitrary code on the affected server. This can lead to a range of malicious activities, including data theft, modification, or destruction, installation of malware, and complete system takeover. Since the vulnerability affects CTMS and CPAS, organizations in sectors utilizing these systems for content or process management are particularly at risk. The vulnerability&rsquo;s high severity allows attackers to quickly gain a foothold and potentially compromise sensitive information or disrupt business operations.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply available patches or updates from Sunnet to address CVE-2026-7490.</li>
<li>Implement the Sigma rule <code>Detect Malicious File Uploads to Web Servers</code> to detect suspicious file uploads based on file extensions and content.</li>
<li>Review and harden file upload functionalities within CTMS and CPAS to prevent arbitrary file uploads.</li>
<li>Monitor web server logs for access to suspicious files in upload directories, using the <code>Web Shell Access</code> Sigma rule.</li>
<li>Restrict access to file upload functionalities to only authorized users with appropriate privileges.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>arbitrary-file-upload</category><category>web-shell</category><category>code-execution</category></item><item><title>livewire-markdown-editor Arbitrary File Upload Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2024-01-02-livewire-markdown-editor-upload/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-02-livewire-markdown-editor-upload/</guid><description>The livewire-markdown-editor versions before v1.3 contain an arbitrary file upload vulnerability in the MarkdownEditor::updatedAttachments() Livewire handler, allowing authenticated users to upload any file type, potentially leading to stored XSS, phishing, malware distribution, and markdown injection.</description><content:encoded><![CDATA[<p>Versions of <code>mckenziearts/livewire-markdown-editor</code> prior to v1.3 are vulnerable to arbitrary file upload via the <code>MarkdownEditor::updatedAttachments()</code> Livewire handler. This handler lacks server-side validation for file types, extensions, and content. An authenticated user with access to a page embedding the markdown editor can upload malicious files (e.g., <code>.html</code>, <code>.svg</code>, <code>.js</code>) to the disk configured by <code>livewire-markdown-editor.disk</code>. If this disk is a public cloud storage bucket (S3, DigitalOcean Spaces, Cloudflare R2, Scaleway Object Storage), the uploaded files are publicly accessible with a guessed <code>Content-Type</code> header. This vulnerability allows attackers to perform stored XSS, host phishing pages, distribute malware, and inject malicious markdown. A real-world exploitation was observed in production.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains access to an application using a vulnerable version of <code>mckenziearts/livewire-markdown-editor</code>.</li>
<li>The attacker navigates to a page embedding the <code>&lt;livewire:markdown-editor&gt;</code> component.</li>
<li>The attacker uses the file upload functionality of the editor to upload a malicious file, such as a <code>.html</code> or <code>.svg</code> file containing XSS payloads.</li>
<li>The <code>MarkdownEditor::updatedAttachments()</code> Livewire handler processes the uploaded file without proper validation.</li>
<li>The handler stores the file on the disk configured by <code>livewire-markdown-editor.disk</code> (e.g., a public cloud bucket like S3, DigitalOcean Spaces, Cloudflare R2, Scaleway Object Storage).</li>
<li>The uploaded file becomes publicly accessible on the storage domain.</li>
<li>A user visits the URL of the uploaded malicious file, triggering the XSS payload or accessing the phishing page.</li>
<li>The attacker achieves their objective, such as stealing user credentials, redirecting users to malicious websites, or compromising the application&rsquo;s integrity.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability can lead to several critical impacts. Stored XSS on the storage domain can allow attackers to steal user credentials or perform other malicious actions in the context of the application. Phishing pages hosted on the application&rsquo;s storage domain can trick users into revealing sensitive information. Malware distribution from a domain users trust can lead to widespread infections. Additionally, markdown injection via crafted filenames can compromise the integrity of the editor&rsquo;s output. A real-world exploitation of this vulnerability was observed in production on a community platform using this package.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to <code>mckenziearts/livewire-markdown-editor</code> v1.3 or later to patch the vulnerability.</li>
<li>If immediate upgrading is not feasible, disable the upload UI on every instance of the editor by passing <code>:show-upload=&quot;false&quot;</code>. This prevents the vulnerable code path from being reached.</li>
<li>Monitor web server logs (category <code>webserver</code>, product <code>linux</code>) for requests to the storage domain for unusual file extensions like <code>.html</code>, <code>.svg</code>, <code>.js</code>, <code>.php</code>, or <code>.exe</code>, which could indicate attempted exploitation.</li>
<li>Implement the file upload detection rule to identify potentially malicious file uploads to the storage domain.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>arbitrary-file-upload</category><category>stored-xss</category><category>vulnerability</category></item></channel></rss>