Security readout for executives and security teams
Plain-English summary
CVE-2026-4329 affects the WordPress plugin Blackhole for Bad Bots through version 3.8. A remote unauthenticated attacker can plant script content in bot log data through the User-Agent header. The script can run later when an administrator opens the plugin’s Bad Bots log page, creating a risk to admin sessions and site integrity.
Executive priority
Treat as high priority for public WordPress sites using this plugin. It does not indicate server takeover by itself, but it can compromise administrator browser sessions and enable follow-on actions inside WordPress. Prioritize inventory, update guidance, and limiting admin exposure.
Technical view
The plugin stores User-Agent-derived bot data after sanitize_text_field(), then outputs stored values in admin HTML attributes and span content without esc_attr() or esc_html(). Wordfence rates this as CVSS 7.2, CWE-79 stored XSS, affecting versions up to and including 3.8. The WordPress Trac references show the relevant storage and rendering locations.
Likely exposure
Exposure is limited to WordPress sites running Blackhole for Bad Bots version 3.8 or earlier. The attack path is network-accessible and unauthenticated, but execution occurs when an administrator views the affected Bad Bots admin page.
Exploitation context
No provided source or KEV entry confirms active exploitation. The issue is practical because attackers can influence User-Agent headers at scale, and bot-blocking plugins commonly collect that data. Administrator interaction with the plugin log page is the execution trigger described by the sources.
Researcher notes
The core weakness is stored XSS from insufficient contextual output encoding. The source description identifies update_option() storage and unsafe rendering in badbots-register.php lines 75-83 and span output. The CVSS vector lists UI:N, but the narrative states execution happens when an administrator views the admin page.
Mitigation direction
- Inventory WordPress sites for Blackhole for Bad Bots versions 3.8 or earlier.
- Check vendor or WordPress plugin guidance for a fixed release and update promptly.
- Restrict administrator access to the plugin log page until remediation is confirmed.
- Avoid viewing suspicious Bad Bots logs on production before patching.
- Back up the site before plugin updates or emergency removal.
Validation and detection
- Confirm installed plugin version across all WordPress environments.
- Review vendor changelog or Trac changeset for escaping fixes.
- Verify output uses esc_attr() for attributes and esc_html() for text content.
- Review stored Bad Bots entries for suspicious User-Agent content.
- Test remediation in staging before administrators revisit affected logs.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-4329 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a71992e2-fdac-4e89-8867-4b771d9b4374?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/blackhole-bad-bots/trunk/inc/badbots-register.php#L75CVE reference
- https://plugins.trac.wordpress.org/browser/blackhole-bad-bots/tags/3.8/inc/badbots-register.php#L79CVE reference
- https://plugins.trac.wordpress.org/browser/blackhole-bad-bots/trunk/inc/blackhole-helpers.php#L22CVE reference
- https://plugins.trac.wordpress.org/browser/blackhole-bad-bots/tags/3.8/inc/blackhole-helpers.php#L22CVE reference
- https://plugins.trac.wordpress.org/browser/blackhole-bad-bots/trunk/inc/blackhole-core.php#L180CVE reference
- https://plugins.trac.wordpress.org/browser/blackhole-bad-bots/tags/3.8/inc/blackhole-core.php#L180CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3487350%40blackhole-bad-bots&new=3487350%40blackhole-bad-bots&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.