dbcve.org
Social Media Share ButtonsWordPress extension · Sygnoos

CVE-2024-2721

HIGH · 8.8 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to after 2.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Deserialization of Untrusted Data vulnerability in Social Media Share Buttons By Sygnoos Social Media Share Buttons.This issue affects Social Media Share Buttons: from n/a through 2.1.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 · moderate confidence

This is a PHP Object Injection/Deserialization vulnerability in the Social Media Share Buttons WordPress plugin. The plugin appears to use PHP's unserialize() function on untrusted user-supplied data, likely from a database or HTTP request. This can allow attackers to inject malicious serialized PHP objects into the application, potentially leading to remote code execution if suitable 'magic methods' exist in the plugin or WordPress environment.

MitigationUpdate to the latest version of Social Media Share Buttons if a patched release is available. If no patch exists, disable and remove the plugin until a fix is released. Review server logs and filesystem for indicators of compromise since this vulnerability may have been exploited.

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
Social Media Share ButtonsWordPress extension
Affected:<= 2.1.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify if Social Media Share Buttons plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder containing 'social-media-share-buttons' or 'sygnoos' in the name
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Determine the installed plugin version
    In WordPress admin, find the plugin in the list and view the version number under the plugin name, or check the plugin's main PHP file for a 'Version' header in the plugin comment block
    Affected if The version is 2.1.0 or lower, or if no version can be determined but the plugin is present
  3. Check if the plugin processes serialized data from untrusted sources
    Search the plugin files for calls to unserialize() function, particularly where input comes from $_GET, $_POST, $_REQUEST, or database fields that could be manipulated by users
    Affected if The plugin code contains unserialize() calls handling user-supplied or database-retrieved data without prior validation
  4. Review for indicators of exploitation
    Examine web server access logs for unusual PHP object injection patterns, check for unexpected files in the /wp-content/ directory, and review WordPress audit logs for suspicious admin actions around the plugin
    Affected if Log entries show serialized payloads in request parameters, or unexpected files/code appear in the plugin directory

If the Social Media Share Buttons plugin is installed at version 2.1.0 or lower and is active, the environment is affected by this PHP Object Injection vulnerability.

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
Upgrade available Upgrade to a release after 2.1.0
Interim mitigation

Update to the latest version of Social Media Share Buttons if a patched release is available. If no patch exists, disable and remove the plugin until a fix is released. Review server logs and filesystem for indicators of compromise since this vulnerability may have been exploited.

Fix this in Social Media Share Buttons Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2721 — 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-2024-2721 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