<?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>Cve-2026-4348 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-4348/</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>Thu, 07 May 2026 06:16:05 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-4348/feed.xml" rel="self" type="application/rss+xml"/><item><title>BetterDocs Pro Plugin SQL Injection Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-betterdocs-sqli/</link><pubDate>Thu, 07 May 2026 06:16:05 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-betterdocs-sqli/</guid><description>The BetterDocs Pro plugin for WordPress is vulnerable to SQL Injection via the `get_current_letter_docs` and `docs_sort_by_letter` AJAX actions, allowing unauthenticated attackers to extract sensitive information from the database.</description><content:encoded><![CDATA[<p>The BetterDocs Pro plugin for WordPress, a popular solution for knowledge base management, is susceptible to a critical SQL Injection vulnerability. This flaw affects all versions up to and including 3.7.0. The vulnerability resides in the <code>get_current_letter_docs</code> and <code>docs_sort_by_letter</code> AJAX actions. A critical prerequisite for exploitation is that the Encyclopedia feature must be enabled within the BetterDocs Pro settings panel. Successful exploitation enables unauthenticated attackers to inject arbitrary SQL queries, potentially leading to sensitive data exfiltration from the WordPress database. This poses a significant risk to the confidentiality and integrity of affected WordPress sites.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a WordPress site using BetterDocs Pro with the Encyclopedia feature enabled.</li>
<li>The attacker crafts a malicious HTTP POST request targeting the <code>wp-admin/admin-ajax.php</code> endpoint.</li>
<li>The crafted request includes the <code>action</code> parameter set to either <code>get_current_letter_docs</code> or <code>docs_sort_by_letter</code>.</li>
<li>The attacker injects malicious SQL code into the <code>limit</code> POST parameter. This parameter is directly interpolated into a SQL query without proper sanitization using <code>$wpdb-&gt;prepare()</code>.</li>
<li>The WordPress server processes the request, executing the attacker-controlled SQL query against the database.</li>
<li>The injected SQL query extracts sensitive information, such as user credentials, configuration data, or other confidential content stored in the database.</li>
<li>The extracted data is returned to the attacker in the HTTP response.</li>
<li>The attacker analyzes the exfiltrated data for valuable information.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL Injection vulnerability can lead to complete compromise of the WordPress database. Attackers can steal sensitive data, including user credentials, API keys, and other confidential information. This could lead to unauthorized access to the WordPress site, data breaches, and potential financial losses. This vulnerability has a CVSS v3.1 base score of 7.5, highlighting the significant risk it poses.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the BetterDocs Pro plugin to a version greater than 3.7.0 to patch CVE-2026-4348.</li>
<li>Deploy the Sigma rule &ldquo;Detect BetterDocs Pro SQL Injection Attempt via limit Parameter&rdquo; to your SIEM to detect exploitation attempts targeting the vulnerable AJAX actions.</li>
<li>Monitor web server logs for suspicious POST requests to <code>wp-admin/admin-ajax.php</code> with the <code>action</code> parameter set to <code>get_current_letter_docs</code> or <code>docs_sort_by_letter</code> and potentially malicious SQL code in the <code>limit</code> parameter.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sqli</category><category>wordpress</category><category>plugin</category><category>cve-2026-4348</category></item></channel></rss>