Superb Social Media Share Buttons And Follow ButtonsWordPress extension · Superbthemes
CVE-2023-29428
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in SuPlugins Superb Social Media Share Buttons and Follow Buttons for WordPress plugin <= 1.1.3 versions.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in SuPlugins Superb Social Media Share Buttons and Follow Buttons WordPress plugin versions 1.1.3 and earlier allows attackers to trick authenticated administrators into executing unintended plugin configuration actions through maliciously crafted HTTP requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Superb Social Media Share Buttons And Follow ButtonsWordPress extension
<= 1.1.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Superb Social Media Share plugin filesCheck the wp-content/plugins/ directory for a folder named 'superb-social-media-share-buttons-and-follow-buttons' or similar variation. Also check wp-content/plugins/ for any folder containing 'superb' and 'social' in the name.Affected if The plugin folder exists in the WordPress plugins directory.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named similar to the folder) or the readme.txt file in the plugin folder. Look for a version comment or the 'Version:' header in the plugin file header.Affected if The version is 1.1.3 or lower, or no version is found (indicating an old installation).
-
Confirm the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and look for the Superb Social Media Share plugin. Check if it shows as 'Active'.Affected if The plugin is activated and accessible to authenticated administrators.
-
Check for admin action endpointsInspect the plugin PHP files for admin menu registrations (add_menu_page, add_options_page) and any form handlers or action parameters that process configuration changes without proper nonce verification.Affected if The plugin contains admin configuration functions that lack CSRF token validation (nonce checks).
If the Superb Social Media Share Buttons plugin is installed, active, and version 1.1.3 or lower, the environment is affected by this CSRF vulnerability.
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 dataUpdate the plugin to the latest version if available; otherwise disable the plugin until a patched version is released, or implement nonce-based CSRF protection in the plugin code.
Fix this in Superb Social Media Share Buttons And Follow Buttons
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29428 — 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-2023-29428 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