{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8911 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8911 is a medium-severity vulnerability in godlessons WP AutoBuzz, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-8911 and fix it if it is affected.\n\nWhat it is: CVE-2026-8911 is a medium-severity vulnerability in godlessons WP AutoBuzz, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-8911 in the wild and no public exploit code.\n\nAffected product: godlessons WP AutoBuzz. 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-8911/ (Markdown: https://insights.sbomify.com/CVE-2026-8911/index.md)","id":"CVE-2026-8911","markdown":"https://insights.sbomify.com/CVE-2026-8911/index.md","name":"CVE-2026-8911","record":{"aliases":["GHSA-62xr-88cq-2vgw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into clicking links to inject malicious scripts via CSRF, bypassing WordPress security filters in the WP AutoBuzz plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","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":"WP AutoBuzz \u003c= 1.1.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'googleAccount' Parameter","id":"CVE-2026-8911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Contest Gallery \u003c= 28.1.6 - Unauthenticated SQL Injection","id":"CVE-2026-8912"},"packages":[],"prev":{"headline":"WP Emoticon Rating \u003c= 1.0.1 - Cross-Site Request Forgery to Reflected Cross-Site Scripting via 'emo_settings' Parameter","id":"CVE-2026-8910"},"products":["WP AutoBuzz"],"published":"2026-05-27","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["godlessons"]},"summary":"Attackers can trick admins into clicking links to inject malicious scripts via CSRF, bypassing WordPress security filters in the WP AutoBuzz plugin.","url":"https://insights.sbomify.com/CVE-2026-8911/"}