<?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>Cve-2026-96871 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-96871/</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>Fri, 02 Oct 2026 08:24:31 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-96871/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>Stored XSS in Mang Board Plugin for WordPress</title><link>https://feed.craftedsignal.io/briefs/2026-10-mang-board-xss/</link><pubDate>Fri, 02 Oct 2026 08:24:31 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-mang-board-xss/</guid><description>The Mang Board plugin for WordPress (&lt;= 2.4.2) is vulnerable to unauthenticated Stored Cross-Site Scripting (XSS) via the 'data_type' parameter, allowing attackers to inject malicious scripts that execute in the context of user browsers.</description><content:encoded><![CDATA[<p>The Mang Board plugin for WordPress is affected by a Stored Cross-Site Scripting (XSS) vulnerability, tracked as CVE-2026-96871, impacting all versions up to and including 2.4.2. The vulnerability arises from insufficient input sanitization and output escaping on the 'data_type' parameter. Because the plugin defaults to guest posting ('write_level=0') and 'editor_type=N' for new boards, the attack vector is exposed to unauthenticated users out-of-the-box. Successful exploitation enables an attacker to inject arbitrary JavaScript into boards, which subsequently executes in the browsers of users viewing the content. This poses a significant risk to administrative sessions and user data within the WordPress environment.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a WordPress site running an vulnerable version of the Mang Board plugin.</li>
<li>Attacker interacts with a publicly accessible board hosted by the plugin.</li>
<li>Attacker submits a POST request to the plugin endpoint containing a malicious payload in the 'data_type' parameter.</li>
<li>The plugin fails to sanitize the input and saves the payload directly into the database.</li>
<li>The server stores the malicious script within the board's data structure.</li>
<li>A victim user (such as an administrator or other user) browses to the compromised page.</li>
<li>The WordPress site serves the page containing the attacker's stored script.</li>
<li>The victim's browser executes the script in the context of the site, leading to session hijacking or unauthorized actions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to execute arbitrary JavaScript in the browsers of visitors. This can result in session hijacking, the theft of sensitive session cookies, unauthorized administrative actions performed on behalf of logged-in users, or the redirection of users to malicious websites. The vulnerability is particularly severe due to the default configuration of the plugin, which permits unauthenticated guest posting on newly created boards.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritize updating the Mang Board plugin to the latest available version that patches CVE-2026-96871. If patching is not immediately feasible, modify the board settings to disable 'write_level=0' (guest posting) or change the 'editor_type' to a restricted mode to limit the exposure of the vulnerable input parameter. Implement a Content Security Policy (CSP) to mitigate the impact of XSS vulnerabilities by restricting the sources from which scripts can be loaded and executed.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>xss</category><category>web-vulnerability</category><category>wordpress</category><category>cve-2026-96871</category></item></channel></rss>