The Security Hardener plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.4. The vulnerability exists because the plugin's user-enumeration protection, which is enabled by default, hooks the rest_endpoints filter via secure_user_endpoints() and overwrites every registered handler's permission_callback on both the /wp/v2/users and /wp/v2/users/(?P[\d]+) routes — including POST, PUT, PATCH, and DELETE handlers — with a bare closure that returns only is_user_logged_in(), completely stripping WordPress Core's original capability checks such as create_users, promote_user, edit_users, and delete_users that WP_REST_Users_Controller normally enforces. This makes it possible for authenticated attackers with Subscriber-level access and above to create new Administrator accounts by sending POST request to /wp/v2/users with administrator role, or to reset an existing Administrator's password by issuing a PUT/POST request to /wp/v2/users/. Because the block_user_enum option defaults to enabled, no special plugin configuration is required — the overwrite is active on every request as soon as the plugin is installed.
CVE-2026-16149
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 22, 2026
Last Modified
August 23, 2026
References (8)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L107
- security@wordfencehttps://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L180
- security@wordfencehttps://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L204
- security@wordfencehttps://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L428
- security@wordfencehttps://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L433
- security@wordfencehttps://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L439
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3630896/security-hardener
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/64f1a71f-e210-4191-bfb4-56f8568180ed?source=cve
Vendor Advisories for CVE-2026-16149(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-23 00:29 UTCEG score recompute
- 2026-08-22 23:36 UTCEG score recompute
- 2026-08-22 23:35 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-16149?
When was CVE-2026-16149 disclosed?
What is the CVSS score of CVE-2026-16149?
How do I remediate CVE-2026-16149?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16149
Is Your Infrastructure Affected by CVE-2026-16149?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.