CVE-2024-31109
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 Toastie Studio Woocommerce Social Media Share Buttons allows Stored XSS.This issue affects Woocommerce Social Media Share Buttons: from n/a through 1.3.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Toastie Studio's Woocommerce Social Media Share Buttons plugin (versions up to 1.3.0) allows attackers to craft malicious requests that, when triggered by an authenticated administrator, injects arbitrary JavaScript into the stored share buttons, leading to Stored XSS. The plugin lacks proper CSRF token validation, enabling attackers to forge administrative actions.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify plugin is installedCheck for the Woocommerce Social Media Share Buttons plugin in your WordPress wp-content/plugins directoryAffected if The plugin directory exists in your WordPress installation
-
Identify installed versionOpen the main plugin PHP file (typically named similar to woocommerce-social-media-share-buttons.php) and locate the Version header comment or version constantAffected if The version number is 1.3.0 or lower
-
Confirm admin action handlers existLocate PHP files handling admin form submissions (usually in admin subfolder or containing 'admin', 'post', 'save' keywords)Affected if Admin action handlers exist in the plugin and process form submissions
-
Check for CSRF protection in admin actionsExamine admin action handler code for nonce verification functions (wp_verify_nonce, wp_create_nonce, check_admin_referer) or CSRF token validationAffected if No nonce or token validation is found in admin action handlers, meaning CSRF protection is missing
-
Verify social buttons are activeCheck WordPress admin panel under plugin settings or widget/shortcode configuration to confirm share buttons are enabled on the siteAffected if Share buttons are configured and active, making the Stored XSS vector viable
You are affected if the plugin is installed with version 1.3.0 or lower, admin actions lack CSRF nonce validation, and social share buttons are actively configured on your site.
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 for all state-changing admin actions and apply proper input sanitization and output encoding for all user-supplied values in social media button rendering to prevent XSS.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31109 — 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-2024-31109 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