CVE-2026-16149

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-23. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 22, 2026

Last Modified

August 24, 2026

References (8)

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 24× in last 7d / 101× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 186 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 20:09 UTCEG score recompute
  2. 2026-10-11 17:21 UTCEG score recompute
  3. 2026-10-11 14:54 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-10 14:21 UTCEG score recompute
  7. 2026-10-10 14:21 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-09 05:07 UTCEG score recompute
  10. 2026-10-09 05:07 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-08 04:24 UTCEG score recompute
  13. 2026-10-08 04:24 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-07 06:41 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-06 19:20 UTCEG score recompute
  17. 2026-10-06 19:20 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-06 07:47 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-05 19:27 UTCEG score recompute
  21. 2026-10-05 19:27 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-05 08:06 UTCEG score recompute
  24. 2026-10-05 08:06 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 75 more
  1. 2026-10-04 20:45 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-10-04 06:44 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-03 19:23 UTCEG score recompute
  4. 2026-10-03 19:23 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-03 07:13 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-02 19:52 UTCEG score recompute
  8. 2026-10-02 19:52 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-02 08:31 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-01 21:10 UTCEG score recompute
  11. 2026-10-01 21:10 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-01 07:41 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-09-30 20:20 UTCEG score recompute
  15. 2026-09-30 20:20 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-09-30 07:23 UTCEG score recompute
  18. 2026-09-30 07:23 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-29 15:20 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-28 22:37 UTCEG score recompute
  22. 2026-09-28 22:36 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-09-28 11:15 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-09-27 23:54 UTCEG score recompute
  26. 2026-09-27 23:54 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  27. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-09-27 12:15 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  29. 2026-09-27 00:55 UTCEG score recompute
  30. 2026-09-27 00:55 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  31. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  32. 2026-09-25 06:17 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-09-24 18:56 UTCEG score recompute
  34. 2026-09-24 18:56 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-09-24 07:21 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  36. 2026-09-23 19:59 UTCEG score recompute
  37. 2026-09-23 19:59 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  38. 2026-09-23 07:00 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-09-22 19:40 UTCEG score recompute
  40. 2026-09-22 19:40 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  41. 2026-09-22 05:08 UTCEG score recompute
  42. 2026-09-22 05:08 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  43. 2026-09-21 17:47 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  44. 2026-09-21 05:40 UTCEG score recompute
  45. 2026-09-21 05:40 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-09-20 17:19 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  47. 2026-09-20 05:58 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-09-19 18:38 UTCEG score recompute
  49. 2026-09-19 18:37 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  50. 2026-09-19 07:17 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-09-18 19:56 UTCEG score recompute
  52. 2026-09-18 19:56 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  53. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  54. 2026-09-18 08:35 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  55. 2026-09-17 21:14 UTCEG score recompute
  56. 2026-09-17 21:14 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  57. 2026-09-17 07:00 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-09-16 19:39 UTCEG score recompute
  59. 2026-09-16 19:39 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  61. 2026-09-16 06:07 UTCEG score recompute
  62. 2026-09-16 06:07 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-09-15 18:46 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  65. 2026-09-15 07:20 UTCEG score recompute
  66. 2026-09-15 07:20 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  67. 2026-09-14 19:59 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-09-14 08:38 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  69. 2026-09-13 21:18 UTCEG score recompute
  70. 2026-09-13 21:18 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  71. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  72. 2026-09-13 09:57 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  73. 2026-09-12 22:37 UTCEG score recompute
  74. 2026-09-12 22:37 UTCGHSA enrichmentGHSA-493r-g3qv-5457 · GitHub severity HIGH · GitHub CVSS 8.8
  75. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16149?
CVE-2026-16149 is a high-severity vulnerability; its CVE record was published on August 22, 2026. 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 restendpoints filter via secureuserendpoints() and…
When was the CVE record for CVE-2026-16149 published?
The CVE record for CVE-2026-16149 was published on August 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 24, 2026; the record at its source may have been updated since.
Is CVE-2026-16149 actively exploited?
CVE-2026-16149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16149?
CVE-2026-16149 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16149?
No fix for CVE-2026-16149 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-16149 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16149

Explore →

Is Your Infrastructure Affected by CVE-2026-16149?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs