CVE-2026-8911
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP AutoBuzz plugin for WordPress has a CSRF vulnerability in versions up to 1.1.1 due to missing nonce validation on a function. This allows unauthenticated attackers to forge administrative requests that update plugin settings with malicious JavaScript. The attack succeeds because the plugin writes unsanitized values directly via update_option, bypassing WordPress's DISALLOW_UNFILTERED_HTML protection and resulting in stored XSS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm WP AutoBuzz plugin is installedCheck your WordPress installation under wp-content/plugins/ for a folder named wp-autobuzz or view the installed plugins list in wp-admin under PluginsAffected if the plugin folder wp-autobuzz exists in the plugins directory
-
Determine the installed plugin versionOpen the main plugin file (wp-autobuzz.php) and locate the Version header comment in the plugin file header, or check the version displayed in the WordPress plugins admin listAffected if the reported version is 1.1.1 or any version lower than 1.1.1
-
Inspect the plugin code for nonce validationLocate the PHP function that handles plugin settings updates (typically containing update_option calls) and search for wp_verify_nonce or check_admin_referer calls within that functionAffected if the settings update function contains no nonce verification logic
-
Check stored plugin options for malicious contentQuery the WordPress database (wp_options table) for option_names related to this plugin (look for options containing 'autobuzz' in the name) and examine the option_value fieldAffected if any plugin option values contain unsanitized HTML or JavaScript tags such as <script> or javascript: URIs
You are affected if the WP AutoBuzz plugin is installed at version 1.1.1 or lower AND the settings update function lacks nonce validation, allowing forged requests to inject malicious scripts into stored options.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd nonce verification to the affected function and sanitize all user input before using update_option. Until the fix is applied, avoid clicking suspicious links while logged into the WordPress admin.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8911 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8911 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data