<?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>Discuz! - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/discuz/</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, 15 Jun 2026 20:19:42 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/discuz/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-49952: Discuz! X5.0 Authentication Bypass Leading to Database Access</title><link>https://feed.craftedsignal.io/briefs/2026-06-discuz-auth-bypass/</link><pubDate>Mon, 15 Jun 2026 20:19:42 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-discuz-auth-bypass/</guid><description>CVE-2026-49952 is an authentication bypass vulnerability in Discuz! X5.0 versions 20260320 through 20260501, allowing unauthenticated remote attackers to gain unauthorized access to database backup and restore functionality by exploiting a shared cryptographic key, leading to potential data exfiltration and user impersonation.</description><content:encoded><![CDATA[<p>A critical authentication bypass vulnerability, identified as CVE-2026-49952, impacts Discuz! X5.0 releases from 20260320 through 20260501. This flaw allows unauthenticated remote attackers to gain unauthorized access to sensitive database backup and restore functionalities. The vulnerability stems from a shared cryptographic key utilized between the UCenter integration and the <code>dbbak.php</code> database backup API. Attackers can leverage an encryption oracle within the <code>logging_ctl::logging_more()</code> function by injecting a specially crafted payload via the username parameter during a login attempt. This manipulation enables them to obtain a legitimately signed token, thereby circumventing standard authorization checks for database operations and potentially triggering a race condition to impersonate arbitrary users. This provides a direct path to sensitive data exfiltration and control over forum content.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated remote attacker identifies a Discuz! X5.0 instance (releases 20260320-20260501) vulnerable to CVE-2026-49952.</li>
<li>The attacker crafts a malicious payload and injects it into the <code>username</code> parameter during a login attempt to the Discuz! instance via a <code>POST</code> request to <code>/member.php</code> or similar login endpoint.</li>
<li>This crafted payload is processed by the <code>logging_ctl::logging_more()</code> function, which contains an encryption oracle due to a shared cryptographic key used by UCenter integration.</li>
<li>By exploiting this encryption oracle, the attacker obtains a legitimately signed authorization token that can bypass further access controls.</li>
<li>The attacker uses the forged token to send direct HTTP requests to the <code>/dbbak.php</code> endpoint, bypassing normal authentication and authorization checks.</li>
<li>Through the <code>/dbbak.php</code> interface, the attacker gains unauthorized access to initiate database export (backup) and import (restore) operations.</li>
<li>The attacker can additionally trigger a race condition during this process to impersonate arbitrary authenticated users within the Discuz! forum.</li>
<li>The final objective is unauthorized access to critical database functions, allowing for data theft, modification, or complete compromise of the forum's content and user data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-49952 grants unauthenticated attackers full control over the Discuz! X5.0 application's database. This includes the ability to export all database contents, leading to mass data exfiltration of user information, private messages, and forum posts. Attackers could also import malicious data, deface the forum, or implant persistent backdoors. The ability to impersonate arbitrary users further exacerbates the risk, allowing attackers to perform actions as legitimate users, including administrative actions if an administrator account is impersonated. Organizations using affected Discuz! X5.0 versions face severe risks of data breach, reputational damage, and operational disruption.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li><strong>Patch CVE-2026-49952 immediately</strong> by upgrading Discuz! X5.0 to a version beyond 20260501 that includes the fix.</li>
<li>Deploy the provided Sigma rules &quot;Detects CVE-2026-49952 Exploitation - Malicious Username Injection Attempt&quot; and &quot;Detects CVE-2026-49952 Exploitation - Unauthorized dbbak.php Access&quot; to your SIEM to detect exploitation attempts.</li>
<li>Enable comprehensive webserver access logging to capture full HTTP request details (URI stem, query, method, user-agent) for your Discuz! instances to facilitate detection and forensics.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>authentication-bypass</category><category>web-vulnerability</category><category>cve</category><category>discuz</category><category>data-exfiltration</category></item></channel></rss>