<?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>Dotnetnuke — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/dotnetnuke/</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, 18 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/dotnetnuke/feed.xml" rel="self" type="application/rss+xml"/><item><title>DNN (DotNetNuke) SVG Upload Vulnerability (CVE-2026-40321)</title><link>https://feed.craftedsignal.io/briefs/2026-04-dnn-svg-upload/</link><pubDate>Sat, 18 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-dnn-svg-upload/</guid><description>DNN (formerly DotNetNuke) before 10.2.2 is vulnerable to stored cross-site scripting (XSS) via malicious SVG file uploads, potentially leading to account takeover and arbitrary code execution.</description><content:encoded><![CDATA[<p>DNN (formerly DotNetNuke) is an open-source web content management system (CMS) built on the .NET framework. Prior to version 10.2.2, a stored cross-site scripting (XSS) vulnerability exists due to insufficient sanitization of SVG files. Attackers can exploit CVE-2026-40321 by uploading a crafted SVG file containing malicious JavaScript. This script can then be executed in the context of other users, including administrators, upon accessing the uploaded SVG. Successful exploitation could lead to session hijacking, account takeover, and potentially arbitrary code execution on the server. Version 10.2.2 addresses this vulnerability by implementing proper sanitization of SVG uploads. The vulnerability affects both authenticated and unauthenticated users, increasing the attack surface.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker identifies a DNN instance running a version prior to 10.2.2.</li>
<li>The attacker crafts a malicious SVG file containing embedded JavaScript code designed to perform actions such as stealing cookies or redirecting users.</li>
<li>The attacker uploads the malicious SVG file to the DNN instance, potentially through a media library or profile picture upload feature.</li>
<li>A user (either authenticated or unauthenticated) views the page or element where the malicious SVG is displayed.</li>
<li>The user&rsquo;s browser executes the embedded JavaScript code within the SVG file.</li>
<li>The malicious script steals the user&rsquo;s session cookie or redirects them to a phishing page.</li>
<li>If the compromised user has administrative privileges, the attacker uses the stolen cookie to access the DNN administration panel.</li>
<li>The attacker leverages their administrative access to inject malicious code into the DNN website or install a backdoor for persistent access.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability (CVE-2026-40321) can lead to a range of negative consequences. Attackers can hijack user sessions, potentially gaining unauthorized access to sensitive data and administrative functions. An attacker can deface the website, inject malware, or steal sensitive information. Because DNN is often used in enterprise environments, this could lead to significant data breaches and reputational damage. The number of affected installations is potentially high, given the widespread use of DNN.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade DNN installations to version 10.2.2 or later to patch CVE-2026-40321, as recommended by the vendor.</li>
<li>Implement the &ldquo;Detect Suspicious SVG Uploads&rdquo; Sigma rule to identify attempts to upload SVG files containing potentially malicious script content.</li>
<li>Monitor web server logs for HTTP requests with the &ldquo;.svg&rdquo; extension and inspect the request body for suspicious JavaScript patterns to proactively detect malicious SVG uploads using the &ldquo;Web Server Suspicious SVG Upload&rdquo; Sigma rule.</li>
<li>Implement strict input validation and sanitization measures for all file uploads, especially SVG files, to prevent the injection of malicious code.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>dnn</category><category>dotnetnuke</category><category>svg</category><category>xss</category><category>cve-2026-40321</category><category>upload</category></item><item><title>DotNetNuke.Core Stored XSS via SVG Upload</title><link>https://feed.craftedsignal.io/briefs/2026-04-dotnetnuke-xss/</link><pubDate>Sat, 11 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-dotnetnuke-xss/</guid><description>DotNetNuke.Core is vulnerable to stored cross-site scripting (XSS) where a user can upload a specially crafted SVG file containing malicious scripts, potentially targeting both authenticated and unauthenticated DNN users, with successful exploitation requiring user interaction and leading to high impact on confidentiality, integrity, and availability.</description><content:encoded><![CDATA[<p>DotNetNuke.Core versions prior to 10.2.2 are vulnerable to stored cross-site scripting (XSS). An attacker can exploit this vulnerability by uploading a malicious SVG file to the DotNetNuke server. This file contains embedded JavaScript that executes when the SVG is processed and displayed by the application. Successful exploitation requires a user to interact with the uploaded SVG file, which then triggers the malicious script execution. This poses a significant risk as the injected scripts can target both authenticated and unauthenticated users, potentially leading to session hijacking, data theft, or unauthorized actions performed on behalf of the victim. This vulnerability was published on April 10, 2026, and patched in version 10.2.2.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker crafts a malicious SVG file containing embedded JavaScript code designed for XSS exploitation.</li>
<li>The attacker, with low privileges, uploads the malicious SVG file to the DotNetNuke server through a file upload functionality.</li>
<li>The server stores the SVG file, making it accessible to other users.</li>
<li>A user (either authenticated or unauthenticated) navigates to the location where the SVG file is stored or displayed.</li>
<li>The user&rsquo;s browser processes the SVG file, triggering the execution of the embedded JavaScript.</li>
<li>The malicious script executes within the user&rsquo;s browser session, gaining access to cookies, session tokens, and other sensitive information.</li>
<li>The attacker steals user&rsquo;s cookies and session tokens.</li>
<li>The attacker uses stolen session tokens to hijack the user&rsquo;s session, perform unauthorized actions, and potentially escalate privileges.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this XSS vulnerability allows an attacker to execute arbitrary JavaScript code within the context of a user&rsquo;s session. This can lead to sensitive information disclosure, such as stealing user credentials or session cookies. An attacker can then hijack user sessions, perform unauthorized actions on their behalf, and potentially gain elevated privileges within the DotNetNuke application. Due to the nature of stored XSS, the impact can be widespread, affecting any user who interacts with the malicious SVG file until the vulnerability is patched.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade DotNetNuke.Core to version 10.2.2 or later to patch the XSS vulnerability (reference: Affected versions).</li>
<li>Implement server-side validation to sanitize uploaded SVG files and prevent the injection of malicious scripts (reference: Description).</li>
<li>Deploy the Sigma rule provided below to detect attempts to upload SVG files containing JavaScript code (reference: Sigma rule &ldquo;Detect SVG Upload with Embedded JavaScript&rdquo;).</li>
<li>Configure web application firewalls (WAFs) to inspect and block suspicious SVG uploads based on content analysis (reference: Description).</li>
<li>Enable logging for file uploads to track potential malicious activity (reference: logsource category &ldquo;file_event&rdquo;).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>dotnetnuke</category><category>xss</category><category>svg</category><category>web-application</category></item></channel></rss>