CVE-2026-9723: Google Plus One Bottom <= 0.0.2 - Cross-Site Request Forgery to Plugin Settings Update via Settings Page
The Google Plus One Bottom plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.0.2. This is due to missing or incorrect nonce validation on the googlePlusOneAdmin function. This makes it possible for unauthenticated attackers to modify the plugin's settings, including the plusone-lang, plusone-callback, and plusone-url options stored in the database via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
A vulnerable WordPress plugin can let an attacker change its settings if they convince an administrator to click or load a crafted request. The expected impact is limited integrity change, not direct data theft or site takeover based on the sources.
Executive priority
Treat as a moderate website hygiene issue. It is unlikely to justify emergency response alone, but affected public WordPress sites should be remediated promptly because administrator-targeted attacks are practical.
Technical view
Google Plus One Bottom versions up to 0.0.2 lack proper nonce validation in the googlePlusOneAdmin settings handler. This enables CSRF against plugin settings such as plusone-lang, plusone-callback, and plusone-url when an authenticated administrator is tricked into interacting with attacker-controlled content.
Likely exposure
Exposure appears limited to WordPress sites running Google Plus One Bottom plugin version 0.0.2 or earlier. The bundle does not identify other affected products or a fixed release.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation. Exploitation requires administrator interaction, so phishing or social engineering is the likely path.
Researcher notes
Evidence supports CWE-352 CSRF caused by missing or incorrect nonce validation in googlePlusOneAdmin. The source bundle names affected options and requires administrator interaction. It does not provide a patch version, exploit-in-the-wild evidence, or broader product impact.
Mitigation direction
Inventory WordPress sites for Google Plus One Bottom version 0.0.2 or earlier.
Disable or remove the plugin where it is not business-critical.
Check vendor and Wordfence guidance for any fixed release or official mitigation.
Review plugin settings for unexpected plusone-lang, plusone-callback, or plusone-url values.
Limit administrator browsing from active WordPress admin sessions.
Validation and detection
Confirm whether the plugin is installed on each WordPress site.
Record installed plugin version and compare against affected versions up to 0.0.2.
Review current plugin option values for unauthorized changes.
Check administrative activity around the publication date for suspicious setting changes.
Verify any remediation against vendor or Wordfence guidance before closing.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-352: 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.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.