CVE-2026-8911
Deferred Deferred - Pending Action
Cross-Site Request Forgery in WP AutoBuzz WordPress Plugin

Publication date: 2026-05-27

Last updated on: 2026-05-27

Assigner: Wordfence

Description
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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-05-27
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
CVE-2026-8911
EUVD
EUVD-2026-32071
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wp_autobuzz wp_autobuzz to 1.1.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The WP AutoBuzz plugin for WordPress has a vulnerability known as Cross-Site Request Forgery (CSRF) in all versions up to and including 1.1.1. This occurs because the plugin lacks proper nonce validation on a function, allowing attackers to trick a site administrator into performing unintended actions, such as clicking a malicious link.

As a result, unauthenticated attackers can update plugin settings and inject malicious web scripts through forged requests. This bypasses WordPress's usual protection mechanisms because the unsanitized data is written directly via the update_option function at the plugin level, outside of WordPress's normal content handling.

Impact Analysis

This vulnerability can allow attackers to inject malicious scripts into your WordPress site by exploiting the plugin's lack of proper validation. This can lead to unauthorized changes in plugin settings and potentially compromise the integrity and security of your website.

Because the attack requires tricking an administrator into clicking a link, it can result in unauthorized actions being performed without the administrator's knowledge, potentially leading to data leakage or site defacement.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-8911. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart