<?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>Plugin Vulnerability — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/plugin-vulnerability/</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, 02 May 2026 12:16:16 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/plugin-vulnerability/feed.xml" rel="self" type="application/rss+xml"/><item><title>Salon Booking System WordPress Plugin Arbitrary File Read Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-wordpress-arbitrary-file-read/</link><pubDate>Sat, 02 May 2026 12:16:16 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-wordpress-arbitrary-file-read/</guid><description>The Salon Booking System WordPress plugin is vulnerable to arbitrary file read, allowing unauthenticated attackers to exfiltrate local files by manipulating file-field values in booking confirmation emails.</description><content:encoded><![CDATA[<p>The Salon Booking System – Free Version plugin for WordPress, versions up to and including 10.30.25, contains an arbitrary file read vulnerability. This flaw stems from the plugin&rsquo;s public booking flow, where it accepts attacker-controlled file-field values. These values are subsequently used as trusted paths when creating email attachments for booking confirmations. This allows an unauthenticated attacker to supply a path to any file accessible to the web server, triggering its inclusion as an attachment in the booking confirmation email, effectively enabling arbitrary file exfiltration. Exploitation requires no authentication and can be triggered remotely.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker accesses the public booking form of a WordPress site running the vulnerable Salon Booking System plugin.</li>
<li>The attacker crafts a malicious request to the booking form, injecting a file path (e.g., <code>/etc/passwd</code>) into a file-field parameter.</li>
<li>The plugin processes the booking request and stores the attacker-supplied file path.</li>
<li>The plugin generates a booking confirmation email.</li>
<li>The plugin uses the stored, attacker-controlled file path to attach the specified file to the confirmation email.</li>
<li>The booking confirmation email, now containing the arbitrary file as an attachment, is sent to the user who initiated the booking (which could be the attacker or an unwitting third party).</li>
<li>The attacker retrieves the email (if sent to the attacker) or intercepts it (if sent to a third party) and extracts the attached file.</li>
<li>The attacker gains unauthorized access to the contents of the exfiltrated file.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows unauthenticated attackers to read arbitrary files from the affected WordPress server. This could lead to the disclosure of sensitive information, such as configuration files, database credentials, or other confidential data. The vulnerability affects versions of the Salon Booking System plugin up to and including 10.30.25. The number of affected WordPress installations is unknown, but could be substantial given the plugin&rsquo;s popularity.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Salon Booking System plugin to the latest version to patch CVE-2026-6320.</li>
<li>Monitor web server logs (category <code>webserver</code>, product <code>linux</code>) for suspicious requests containing absolute or relative file paths in file-field parameters, using a detection rule similar to the ones provided below.</li>
<li>Implement strict input validation and sanitization for all user-supplied data, especially file paths.</li>
<li>Review and restrict file system permissions to limit the files accessible to the web server process.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>arbitrary-file-read</category><category>wordpress</category><category>plugin-vulnerability</category><category>cve</category></item><item><title>WP Mail Gateway Plugin Vulnerability Leads to Privilege Escalation</title><link>https://feed.craftedsignal.io/briefs/2026-05-wp-mail-gateway-privesc/</link><pubDate>Sat, 02 May 2026 05:16:01 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-wp-mail-gateway-privesc/</guid><description>The WP Mail Gateway plugin for WordPress is vulnerable to unauthorized access due to a missing capability check, allowing authenticated attackers to modify SMTP settings and escalate privileges.</description><content:encoded><![CDATA[<p>The WP Mail Gateway plugin, a WordPress extension, contains a vulnerability (CVE-2026-6963) that allows authenticated users with minimal privileges (Subscriber level or higher) to gain administrative access. The flaw resides in the <code>wmg_save_provider_config</code> AJAX action, which lacks proper authorization checks. This omission enables attackers to manipulate SMTP settings, redirect outgoing emails, and ultimately trigger password reset emails intended for administrators. The vulnerability affects all versions of the WP Mail Gateway plugin up to and including version 1.8. Successful exploitation grants attackers complete control over the WordPress site, making it a critical security concern for any organization using the vulnerable plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker logs into a WordPress site with a Subscriber-level account or higher.</li>
<li>The attacker crafts a malicious AJAX request targeting the <code>wmg_save_provider_config</code> action.</li>
<li>This request modifies the SMTP settings, redirecting outgoing emails to an attacker-controlled server.</li>
<li>The attacker initiates a password reset request for an administrator account.</li>
<li>The password reset email is intercepted by the attacker&rsquo;s server.</li>
<li>The attacker uses the password reset link to gain access to the administrator&rsquo;s account.</li>
<li>The attacker logs into the WordPress dashboard with administrator privileges.</li>
<li>The attacker can now perform any administrative action, including installing malicious plugins, modifying site content, or creating new administrator accounts.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-6963 allows an attacker to completely compromise a WordPress website.  Even low-privileged users can elevate their access to administrator, giving them full control over the site.  This can lead to data breaches, website defacement, malware deployment, and other malicious activities. The vulnerability affects all installations of the WP Mail Gateway plugin up to version 1.8, potentially impacting thousands of WordPress sites.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the WP Mail Gateway plugin to a version beyond 1.8 to patch CVE-2026-6963.</li>
<li>Monitor WordPress logs for suspicious AJAX requests targeting the <code>wmg_save_provider_config</code> action using the Sigma rule provided below. Enable webserver logging to capture HTTP POST requests.</li>
<li>Implement the provided Sigma rule to detect modifications to WordPress options related to SMTP configuration. Enable relevant logging for registry modifications.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>wordpress</category><category>privilege-escalation</category><category>plugin-vulnerability</category></item><item><title>WordPress Temporary Login Plugin Authentication Bypass (CVE-2026-7567)</title><link>https://feed.craftedsignal.io/briefs/2024-01-wordpress-temp-login-auth-bypass/</link><pubDate>Fri, 01 May 2026 10:15:58 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-wordpress-temp-login-auth-bypass/</guid><description>The Temporary Login plugin for WordPress versions up to 1.0.0 is vulnerable to authentication bypass due to improper input validation, allowing unauthenticated attackers to log in as arbitrary temporary users by sending a specially crafted GET request.</description><content:encoded><![CDATA[<p>CVE-2026-7567 is an authentication bypass vulnerability that affects the Temporary Login plugin for WordPress, specifically versions up to and including 1.0.0. The vulnerability stems from a failure to properly validate the &rsquo;temp-login-token&rsquo; GET parameter within the <code>maybe_login_temporary_user()</code> function. By supplying an array as the value for this parameter, attackers can circumvent the intended <code>empty()</code> check. This leads to the <code>sanitize_key()</code> function returning an empty string, which is then used in a database query to fetch users. WordPress ignores empty <code>meta_value</code> parameters, causing the query to return all users with the <code>_temporary_login_token</code> meta key. Consequently, an unauthenticated attacker can effectively authenticate as any user with an active temporary login session by sending a single, maliciously crafted GET request. This poses a severe risk to website security, as it allows unauthorized access to user accounts and potentially sensitive data.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a WordPress site using the vulnerable Temporary Login plugin (version &lt;= 1.0.0).</li>
<li>The attacker crafts a malicious GET request targeting the WordPress site&rsquo;s login endpoint, including the &rsquo;temp-login-token&rsquo; parameter as an array (e.g., <code>temp-login-token[]=</code>).</li>
<li>The web server receives the GET request.</li>
<li>The <code>maybe_login_temporary_user()</code> function processes the request.</li>
<li>Due to improper input validation, the <code>empty()</code> check is bypassed when the &rsquo;temp-login-token&rsquo; parameter is an array.</li>
<li><code>sanitize_key()</code> processes the array and returns an empty string as the meta_value.</li>
<li>WordPress executes a database query using the empty meta_value, effectively retrieving all users with active temporary login tokens.</li>
<li>The attacker is granted unauthorized access to the account of a targeted temporary user, bypassing normal authentication procedures.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-7567 allows unauthenticated attackers to bypass login restrictions and gain unauthorized access to WordPress user accounts utilizing the vulnerable Temporary Login plugin. The severity is high, as it allows complete compromise of user accounts without requiring any valid credentials. The impact includes potential data theft, account takeover, website defacement, and other malicious activities, depending on the privileges of the compromised user account.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the available patch or upgrade the Temporary Login plugin to a version greater than 1.0.0 to remediate CVE-2026-7567.</li>
<li>Deploy the Sigma rule <code>Detect WordPress Temporary Login Authentication Bypass Attempt</code> to detect exploitation attempts by monitoring HTTP requests with array-based <code>temp-login-token</code> parameters in the query string.</li>
<li>Implement input validation on the web server to reject requests containing array-based parameters where scalar strings are expected.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>authentication bypass</category><category>wordpress</category><category>plugin vulnerability</category><category>cve-2026-7567</category><category>cloud</category></item><item><title>WordPress Create DB Tables Plugin Authorization Bypass Vulnerability (CVE-2026-4119)</title><link>https://feed.craftedsignal.io/briefs/2026-04-wordpress-create-db-tables-auth-bypass/</link><pubDate>Wed, 22 Apr 2026 09:16:49 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-wordpress-create-db-tables-auth-bypass/</guid><description>The Create DB Tables plugin for WordPress versions 1.2.1 and earlier is vulnerable to an authorization bypass, allowing authenticated users to create and delete database tables without proper checks, potentially leading to complete site destruction.</description><content:encoded><![CDATA[<p>The Create DB Tables plugin, versions 1.2.1 and earlier, suffers from an authorization bypass vulnerability (CVE-2026-4119). This flaw stems from the plugin&rsquo;s failure to implement capability checks or nonce verification for its admin_post action hooks, specifically those responsible for creating (admin_post_add_table) and deleting (admin_post_delete_db_table) database tables. Because the admin_post hook only requires a user to be logged in, any authenticated user, including those with the lowest Subscriber role, can access these endpoints. This oversight allows malicious actors to create arbitrary database tables or, more critically, delete existing ones, including vital WordPress core tables. The vulnerability was published on 2026-04-22, and given the severity, defenders should immediately address this risk. The affected versions of the plugin should be updated or removed to prevent potential exploitation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker registers an account on a vulnerable WordPress site, gaining Subscriber-level access.</li>
<li>The attacker crafts a POST request to <code>wp-admin/admin-post.php</code> with the action parameter set to <code>add_table</code> or <code>delete_db_table</code>.</li>
<li>The attacker provides the <code>db_table</code> parameter with the name of the table to be deleted, if exploiting the <code>delete_db_table</code> action.</li>
<li>The server processes the request without proper authorization checks, because <code>current_user_can()</code> and <code>wp_verify_nonce()</code> are missing.</li>
<li>The <code>cdbt_delete_db_table()</code> function executes a <code>DROP TABLE</code> SQL query based on the user-supplied <code>db_table</code> parameter.</li>
<li>If the attacker targets a critical WordPress core table like <code>wp_users</code> or <code>wp_options</code>, the site&rsquo;s functionality will be severely impacted.</li>
<li>Alternatively, if exploiting the <code>add_table</code> action, the <code>cdbt_create_new_table()</code> function executes a <code>CREATE TABLE</code> SQL query, creating an arbitrary database table.</li>
<li>Successful exploitation can lead to complete destruction of the WordPress installation or the introduction of malicious database tables.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows any authenticated user to delete arbitrary database tables, including critical WordPress core tables. This can lead to complete site destruction and data loss. An attacker could delete the <code>wp_users</code> table, effectively locking out all administrators and other users, or delete the <code>wp_options</code> table, causing the site to revert to its default state or become completely unusable. The CVSS v3.1 base score for this vulnerability is 9.1, highlighting the critical nature of the risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately update the Create DB Tables plugin to a version higher than 1.2.1, where this vulnerability is patched.</li>
<li>Monitor web server logs for POST requests to <code>wp-admin/admin-post.php</code> with <code>action=delete_db_table</code> or <code>action=add_table</code> (see rule: &ldquo;Detect Unauthorized DB Table Modification&rdquo;).</li>
<li>Implement a Web Application Firewall (WAF) rule to block requests to <code>wp-admin/admin-post.php</code> with the vulnerable actions unless originating from an administrator (see rule: &ldquo;WAF - Block Unauthorized DB Table Modification&rdquo;).</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>wordpress</category><category>authorization-bypass</category><category>plugin-vulnerability</category><category>cve-2026-4119</category></item><item><title>Media Library Assistant WordPress Plugin SQL Injection Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-mla-sql-injection/</link><pubDate>Mon, 06 Apr 2026 15:17:11 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-mla-sql-injection/</guid><description>The Media Library Assistant WordPress plugin through version 3.34 is vulnerable to SQL injection, allowing attackers to manipulate database queries.</description><content:encoded><![CDATA[<p>CVE-2026-34885 describes an SQL Injection vulnerability affecting the Media Library Assistant WordPress plugin. This plugin, developed by David Lingren, is vulnerable in versions up to and including 3.34. The vulnerability stems from improper neutralization of special elements used in SQL commands, potentially allowing attackers to inject malicious SQL code. Exploitation could lead to unauthorized data access, modification, or deletion within the WordPress database. Given the widespread use of WordPress and its plugin ecosystem, this vulnerability presents a significant risk to websites utilizing the affected plugin. Successful exploitation could compromise sensitive information, deface websites, or even gain administrative control.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker identifies a WordPress website using Media Library Assistant version 3.34 or earlier.</li>
<li>The attacker crafts a malicious HTTP request containing SQL injection payload in a plugin parameter, such as a search query or media metadata field.</li>
<li>The crafted request is sent to the vulnerable endpoint within the Media Library Assistant plugin.</li>
<li>The plugin fails to properly sanitize or neutralize the SQL injection payload.</li>
<li>The unsanitized payload is incorporated into an SQL query executed against the WordPress database.</li>
<li>The injected SQL code manipulates the query logic, allowing the attacker to bypass security checks.</li>
<li>The attacker extracts sensitive data from the database, such as user credentials, posts, or other stored information.</li>
<li>The attacker could potentially modify or delete data, or even gain administrative access to the WordPress site.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL injection vulnerability could lead to a range of damaging outcomes. Attackers could gain unauthorized access to sensitive data stored within the WordPress database, including user credentials, customer information, and proprietary content. This data could be exfiltrated and sold on the dark web or used for further malicious activities. Website defacement, data modification, and complete site compromise are also potential consequences. The number of affected websites is potentially large, given the popularity of WordPress and its extensive plugin ecosystem.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Media Library Assistant WordPress plugin to a version higher than 3.34 to patch CVE-2026-34885.</li>
<li>Deploy the Sigma rule <code>Detect SQL Injection Attempts via HTTP Request</code> to identify potential exploitation attempts in web server logs.</li>
<li>Implement a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL injection attacks against WordPress plugins.</li>
<li>Enable regular security audits of WordPress installations and plugins to identify and address vulnerabilities promptly.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sql-injection</category><category>wordpress</category><category>plugin-vulnerability</category></item><item><title>Contest Gallery WordPress Plugin Authentication Bypass Vulnerability (CVE-2026-4021)</title><link>https://feed.craftedsignal.io/briefs/2026-03-contest-gallery-auth-bypass/</link><pubDate>Tue, 24 Mar 2026 00:16:31 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-contest-gallery-auth-bypass/</guid><description>CVE-2026-4021 describes an authentication bypass vulnerability in the Contest Gallery plugin for WordPress, allowing unauthenticated attackers to gain admin access by manipulating the user activation key and using an AJAX login endpoint.</description><content:encoded><![CDATA[<p>The Contest Gallery plugin for WordPress, versions up to and including 28.1.5, is vulnerable to a critical authentication bypass (CVE-2026-4021). This vulnerability stems from how the <code>users-registry-check-after-email-or-pin-confirmation.php</code> script handles email confirmations, combined with an unauthenticated key-based login endpoint in <code>ajax-functions-frontend.php</code>.  If the <code>RegMailOptional=1</code> setting is enabled (non-default), an attacker can register a new user account with a specially…</p>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>wordpress</category><category>authentication-bypass</category><category>plugin-vulnerability</category><category>cve-2026-4021</category></item></channel></rss>