<?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>Security Hardener - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/security-hardener/</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>Sun, 23 Aug 2026 01:34:06 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/security-hardener/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>Authorization Bypass in Security Hardener Plugin for WordPress</title><link>https://feed.craftedsignal.io/briefs/2026-08-security-hardener-vuln/</link><pubDate>Sun, 23 Aug 2026 01:34:06 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-security-hardener-vuln/</guid><description>The Security Hardener plugin for WordPress contains an authorization bypass vulnerability in versions 2.4.4 and earlier that allows authenticated subscribers to escalate privileges to administrator.</description><content:encoded><![CDATA[<p>The Security Hardener plugin for WordPress (versions 2.4.4 and earlier) contains a critical Missing Authorization vulnerability, assigned CVE-2026-16149. The flaw stems from the plugin's user-enumeration protection feature, which hooks into the WordPress <code>rest_endpoints</code> filter. Specifically, the <code>secure_user_endpoints()</code> function incorrectly overwrites the permission callbacks for the <code>/wp/v2/users</code> and <code>/wp/v2/users/(?P&lt;id&gt;[\d]+)</code> REST API routes.</p>
<p>By replacing WordPress Core's granular capability checks - such as <code>create_users</code>, <code>promote_user</code>, <code>edit_users</code>, and <code>delete_users</code> - with a simplistic <code>is_user_logged_in()</code> check, the plugin inadvertently permits any authenticated user to perform administrative actions. Since this protection feature is enabled by default upon installation, no specific configuration is required for an attacker to exploit the flaw. Successful exploitation allows a standard Subscriber account to create new Administrator accounts or overwrite the credentials of existing administrative users via crafted REST API requests.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in full administrative takeover of the WordPress site. An attacker can create new administrator accounts, delete content, modify site configuration, or gain remote code execution capabilities through administrative features like plugin/theme management. The vulnerability affects any WordPress instance where the Security Hardener plugin is active, posing a significant risk to site integrity and data security.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the Security Hardener plugin to the latest version immediately to patch CVE-2026-16149.</li>
<li>Audit existing user accounts for suspicious additions or modifications, specifically looking for new users created with administrator roles.</li>
<li>Review WordPress REST API access logs for anomalous POST, PUT, PATCH, or DELETE requests directed at the <code>/wp-json/wp/v2/users</code> endpoint originating from low-privileged accounts.</li>
<li>If patching is not immediately feasible, disable the user-enumeration protection feature within the Security Hardener plugin settings.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>