Simple Share Buttons AdderWordPress extension · Simplesharebuttons
CVE-2022-47178
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 Simple Share Buttons Simple Share Buttons Adder plugin <= 8.4.7 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 the Simple Share Buttons Adder WordPress plugin versions 8.4.7 and below allows attackers to execute unintended actions on behalf of authenticated users by tricking them into submitting malicious 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
Simple Share Buttons AdderWordPress extension
<= 8.4.7CVSS 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 Simple Share Buttons Adder plugin directoryCheck the WordPress plugins folder at wp-content/plugins/ for a directory named 'simple-share-buttons-adder' or similar variant containing 'share-buttons' in the nameAffected if The plugin directory exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin PHP file (usually the primary .php file in the plugin directory) and locate the version string in the plugin header comment (e.g., 'Version: x.x.x')Affected if The version number is 8.4.7 or lower, or if no version is declared and the plugin is present
-
Verify the plugin is activeAccess the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and check if Simple Share Buttons Adder is listed as 'Active'Affected if The plugin shows as activated in the WordPress admin plugins list
-
Confirm state-changing admin actions lack CSRF protectionReview the plugin source code for form submissions and admin action handlers (POST/GET requests to admin.php?page=) and verify whether wp_nonce_field(), wp_verify_nonce(), or similar nonce verification functions are usedAffected if State-changing operations (settings saves, button configuration updates) do not implement nonce verification
The environment is affected if the Simple Share Buttons Adder plugin is installed and active at version 8.4.7 or below, and admin actions lack nonce/CSRF token validation.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing operations (admin actions, settings updates) and validate the Origin/Referer headers to ensure requests originate from legitimate sources.
Fix this in Simple Share Buttons Adder
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47178 — 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-2022-47178 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