dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-34904

HIGH · 7.5 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Analytify Simple Social Media Share Buttons allows Cross Site Request Forgery.This issue affects Simple Social Media Share Buttons: from n/a through 6.2.0.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Analytify Simple Social Media Share Buttons WordPress plugin allows unauthenticated attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or share button configurations.

MitigationUpdate to the latest version of Simple Social Media Share Buttons which implements proper anti-CSRF token (nonce) validation on all state-changing operations including plugin settings and button configuration forms.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed and active
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and locate 'Simple Social Media Share Buttons' by Analytify. Verify the plugin is activated.
    Affected if The plugin is installed and active with no version information available for comparison.
  2. Identify the installed plugin version
    In the WordPress plugins list, click on the plugin name to view details, or check the plugin's main PHP file header for the 'Version' comment tag.
    Affected if The installed version cannot be compared to a fixed affected range because no specific vulnerable versions were provided.
  3. Inspect plugin settings pages for CSRF protection
    Navigate to the plugin's settings page (usually under Settings or the plugin's own menu). Use browser developer tools to view the HTML source of any form that modifies settings or button configurations. Look for an input field named '_wpnonce' or 'nonce' with a hidden type.
    Affected if The settings forms or share button configuration forms lack a CSRF token (nonce) field, indicating the vulnerability is present.
  4. Check plugin PHP code for nonce validation
    Access the plugin files via FTP or file manager. Open the PHP file that handles form submissions (usually named admin.php, settings.php, or similar). Search for the presence of 'wp_verify_nonce' or 'check_admin_referer' functions before any state-changing operations.
    Affected if The plugin's form handling code does not verify a nonce before processing settings or button configuration changes.
  5. Verify state-changing operations are unprotected
    Submit a settings change request (such as modifying button labels or share options) using an external tool like curl, without including any CSRF token. If the request succeeds, the plugin lacks CSRF protection.
    Affected if The plugin accepts and processes configuration changes without requiring a valid CSRF token, confirming the vulnerability.

If the plugin is installed and its settings/button configuration forms do not include WordPress nonce validation, the environment is vulnerable to CVE-2026-34904.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Simple Social Media Share Buttons which implements proper anti-CSRF token (nonce) validation on all state-changing operations including plugin settings and button configuration forms.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34904 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34904 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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