{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4329 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4329 is a high-severity cross-site scripting vulnerability in specialk Blackhole for Bad Bots, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4329 and fix it if it is affected.\n\nWhat it is: CVE-2026-4329 is a high-severity cross-site scripting vulnerability in specialk Blackhole for Bad Bots, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-4329 in the wild and no public exploit code.\n\nAffected product: specialk Blackhole for Bad Bots. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4329/ (Markdown: https://insights.sbomify.com/CVE-2026-4329/index.md)","id":"CVE-2026-4329","markdown":"https://insights.sbomify.com/CVE-2026-4329/index.md","name":"CVE-2026-4329","record":{"aliases":["GHSA-cpmh-vq2q-hhp7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject scripts via User-Agent headers that execute when admins view the plugin's log page, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Blackhole for Bad Bots \u003c= 3.8 - Unauthenticated Stored Cross-Site Scripting via User-Agent HTTP Header","id":"CVE-2026-4329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":12,"next":{"headline":"Missing authorization in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2026-4330"},"packages":[],"prev":{"headline":"Server-side request forgery in Advanced Import","id":"CVE-2026-4328"},"products":["Blackhole for Bad Bots"],"published":"2026-03-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["specialk"]},"summary":"Unauthenticated attackers can inject scripts via User-Agent headers that execute when admins view the plugin's log page, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-4329/"}