CVE-2026-16149 is a missing authorization vulnerability in the Security Hardener plugin for WordPress affecting all versions up to and including 2.4.4. The flaw is introduced by the plugin’s user-enumeration protection logic, enabled by default, which hooks the WordPress rest_endpoints filter through the secure_user_endpoints() function and replaces the permission_callback for the WordPress REST API user routes with a closure that only checks whether the requester is authenticated. In doing so, it strips the original authorization checks normally enforced by WP_REST_Users_Controller on the user-management endpoints, including capability checks such as create_users, promote_user, edit_users, and delete_users. The affected routes include the core user collection and individual user endpoints, and the overwrite impacts write operations such as POST, PUT, PATCH, and DELETE. As a result, any authenticated user with Subscriber-level access or higher can invoke privileged user-management actions that should be restricted to higher-privileged roles, including creating a new administrator account or modifying an existing administrator account to reset its password.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.