<?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/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Laradashboard (&lt;= 1.2.2) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/laradashboard--1.2.2/</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>Mon, 07 Sep 2026 23:37:52 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/laradashboard--1.2.2/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Arbitrary File Upload and RCE in Lara Dashboard</title><link>https://feed.craftedsignal.io/briefs/2026-09-lara-dashboard-rce/</link><pubDate>Mon, 07 Sep 2026 23:37:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-lara-dashboard-rce/</guid><description>Lara Dashboard versions prior to 1.3.2 are vulnerable to arbitrary file upload via the core-upgrades endpoint, allowing unauthorized administrators to achieve remote code execution.</description><content:encoded><![CDATA[<p>Lara Dashboard versions before 1.3.2 contain an authorization flaw in the /admin/settings/core-upgrades/upload endpoint. The application incorrectly restricts access to this endpoint to the 'settings.edit' permission rather than enforcing 'Superadmin' status. This vulnerability allows an authenticated administrator with limited permissions to upload and extract arbitrary ZIP archives. By crafting a malicious archive, an attacker can overwrite critical application files, such as 'routes/web.php', with payloads containing system commands. These commands execute in the context of the web server user, providing the attacker with full control over the application environment, including access to database credentials and environment secrets. This attack allows for persistence and full system compromise, impacting the confidentiality, integrity, and availability of the host application.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to the Lara Dashboard using valid administrative credentials that possess the 'settings.edit' permission.</li>
<li>Attacker navigates to the core-upgrades administrative panel within the dashboard interface.</li>
<li>Attacker crafts a malicious ZIP archive containing weaponized PHP files designed to overwrite existing application source code.</li>
<li>Attacker performs an HTTP POST request to '/admin/settings/core-upgrades/upload' containing the malicious ZIP archive.</li>
<li>The application validates the 'settings.edit' permission and proceeds to extract the archive to the web application's root directory.</li>
<li>The uploaded malicious PHP files overwrite legitimate application source code, such as 'routes/web.php'.</li>
<li>Attacker triggers the execution of the injected code by requesting the modified PHP file via a browser or script.</li>
<li>Arbitrary system commands are executed with the privileges of the web server user, resulting in credential exfiltration or full system compromise.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation leads to full remote code execution, enabling attackers to extract sensitive environment secrets, access database credentials, and gain persistence on the server. The target is the Lara Dashboard application, specifically affecting installations prior to version 1.3.2.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritize the upgrade of all Lara Dashboard instances to version 1.3.2 or later to address the insufficient authorization check on the file upload endpoint.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application-vulnerability</category><category>rce</category><category>file-upload</category><category>path-traversal</category><category>web-vulnerability</category></item></channel></rss>