Skip to main content
VulnerabilityPublished Updated

CVE-2026-16149: Security Hardener (WordPress plugin) · Improper Privilege Management

Affects Security Hardener (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
marc4Security HardenerAffected
  • <=2.4.4
Fixed in–

AI-suggested

Until a fix is available, consider disabling the Security Hardener plugin or the user-enumeration protection feature if possible. Monitor for plugin updates from the vendor that address this authorization bypass vulnerability.

Description

The Security Hardener plugin for WordPress versions up to and including 2.4.4 contains an authorization bypass vulnerability. This flaw arises because the plugin overwrites permission callbacks on user-related REST API endpoints, removing WordPress's core capability checks. As a result, authenticated users with Subscriber-level access or higher can create new Administrator accounts or reset passwords of existing Administrators without proper authorization. The vulnerability is active by default due to the enabled user-enumeration protection feature.

References

Community reviews

Loading reviews…