CVE-2026-4329

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-03-26. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

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

The Blackhole for Bad Bots plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the User-Agent HTTP header in all versions up to and including 3.8. This is due to insufficient input sanitization and output escaping. The plugin uses sanitize_text_field() when capturing bot data (which strips HTML tags but does not escape HTML entities like double quotes), then stores the data via update_option(). When an administrator views the Bad Bots log page, the stored data is output directly into HTML input value attributes (lines 75-83) without esc_attr() and into HTML span content without esc_html(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the Blackhole Bad Bots admin page.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
48(Track)
EG Risk 48/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
Severity72% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

March 26, 2026

Last Modified

June 17, 2026

References (12)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 29× 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.

Showing the most recent 100 of 101 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-4329?
CVE-2026-4329 is a high vulnerability published on March 26, 2026. The Blackhole for Bad Bots plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the User-Agent HTTP header in all versions up to and including 3.8. This is due to insufficient input sanitization and output escaping. The plugin uses sanitizetextfield() when capturing bot data (which…
When was CVE-2026-4329 disclosed?
CVE-2026-4329 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4329 actively exploited?
CVE-2026-4329 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-4329?
CVE-2026-4329 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-4329?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4329, 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-4329

Explore →

Is Your Infrastructure Affected by CVE-2026-4329?

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

Start Free Scan →Browse All CVEs