CVE-2026-8911

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

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

The WP AutoBuzz plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This vulnerability bypasses WordPress's DISALLOW_UNFILTERED_HTML protection because the unsanitized value is written directly via update_option at the plugin level, entirely outside of WordPress post content handling.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
28(Track)
EG Risk 28/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 computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
4.2%
KEV
Not listed

Published

May 27, 2026

Last Modified

May 27, 2026

References (4)

Vendor Advisories for CVE-2026-8911(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 9× in last 7d / 38× 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.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:23 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-01 15:07 UTCEPSS rescore
Show 60 more
  1. 2026-07-01 11:46 UTCGHSA enrichment
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 21:42 UTCGHSA enrichment
  4. 2026-06-29 14:06 UTCEPSS rescore
  5. 2026-06-28 22:01 UTCGHSA enrichment
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-27 18:46 UTCGHSA enrichment
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 17:22 UTCGHSA enrichment
  10. 2026-06-25 13:50 UTCEPSS rescore
  11. 2026-06-25 09:23 UTCGHSA enrichment
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 01:59 UTCEPSS rescore
  17. 2026-06-19 19:26 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-17 21:48 UTCGHSA enrichment
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-16 22:07 UTCGHSA enrichment
  22. 2026-06-16 17:53 UTCEPSS rescore
  23. 2026-06-15 22:26 UTCGHSA enrichment
  24. 2026-06-15 17:49 UTCEPSS rescore
  25. 2026-06-15 17:49 UTCEPSS rescore
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-14 21:30 UTCGHSA enrichment
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 21:49 UTCGHSA enrichment
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 22:07 UTCGHSA enrichment
  33. 2026-06-11 22:26 UTCGHSA enrichment
  34. 2026-06-11 14:00 UTCEPSS rescore
  35. 2026-06-10 22:46 UTCGHSA enrichment
  36. 2026-06-10 22:19 UTCEPSS rescore
  37. 2026-06-10 13:22 UTCEPSS rescore
  38. 2026-06-09 23:04 UTCGHSA enrichment
  39. 2026-06-08 23:23 UTCGHSA enrichment
  40. 2026-06-08 14:17 UTCEPSS rescore
  41. 2026-06-07 23:42 UTCGHSA enrichment
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 00:01 UTCGHSA enrichment
  44. 2026-06-06 00:19 UTCGHSA enrichment
  45. 2026-06-05 22:47 UTCEPSS rescore
  46. 2026-06-05 06:10 UTCEPSS rescore
  47. 2026-06-05 00:38 UTCGHSA enrichment
  48. 2026-06-04 13:12 UTCEPSS rescore
  49. 2026-06-04 00:57 UTCGHSA enrichment
  50. 2026-06-03 01:15 UTCGHSA enrichment
  51. 2026-06-02 20:13 UTCEPSS rescore
  52. 2026-06-02 01:34 UTCGHSA enrichment
  53. 2026-06-01 13:52 UTCEPSS rescore
  54. 2026-06-01 01:53 UTCGHSA enrichment
  55. 2026-05-31 22:30 UTCEPSS rescore
  56. 2026-05-31 00:16 UTCEPSS rescore
  57. 2026-05-29 13:44 UTCEPSS rescore
  58. 2026-05-28 13:44 UTCEPSS rescore
  59. 2026-05-27 13:40 UTCEPSS rescore
  60. 2026-05-27 06:35 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8911?
CVE-2026-8911 is a medium vulnerability published on May 27, 2026. The WP AutoBuzz plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts…
When was CVE-2026-8911 disclosed?
CVE-2026-8911 was first published in the National Vulnerability Database on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8911 actively exploited?
CVE-2026-8911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8911?
CVE-2026-8911 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-8911?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8911, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8911?

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

Start Free Scan →Browse All CVEs