dbcve.org
Social Media Share ButtonsWordPress extension · Sygnoos

CVE-2024-1685

HIGH · 8.8 CVSS v3.1 Published 2024-03-16
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
The Social Media Share Buttons plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.1.0 via deserialization of untrusted input through the attachmentUrl parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. CVE-2024-2721 is likely a duplicate to this issue.

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

The Social Media Share Buttons WordPress plugin versions up to 2.1.0 are vulnerable to PHP Object Injection via the attachmentUrl parameter, which deserializes untrusted input without proper validation. Authenticated attackers with subscriber-level access can inject arbitrary PHP objects. While no POP chain exists in the plugin itself, a POP chain from another plugin/theme on the target system could enable remote code execution, arbitrary file deletion, or data exfiltration.

MitigationUpdate the plugin to a patched version once available, or remove the plugin if no update exists. Additionally, audit the WordPress environment for other plugins/themes that could provide a POP chain, and consider restricting user registration to minimize the attack surface.

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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Sygnoos Social Media Share Buttons' or check the wp-content/plugins directory for a folder containing 'social-media-share' or similar Sygnoos-related naming.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed version
    In WordPress admin Plugins list, find the plugin and view the version number displayed, or read the main plugin PHP file and look for a Version: header comment.
    Affected if Version is 2.1.0 or lower
  3. Confirm user registration is accessible to untrusted users
    In WordPress admin, go to Settings > General and check 'Membership - Anyone can register' is enabled, then verify the default New User Role is set to 'Subscriber' or a low-privilege role.
    Affected if Anyone can register and new users get subscriber-level or higher access
  4. Verify the vulnerable endpoint is accessible
    Check if the WordPress site is publicly accessible and the plugin exposes an endpoint that accepts the attachmentUrl parameter. This typically involves inspecting the plugin code for functions handling URL parameters and unserialize() calls.
    Affected if The plugin handles the attachmentUrl parameter with unserialize() and this functionality is accessible to authenticated users

The environment is affected if the Sygnoos Social Media Share Buttons plugin version 2.1.0 or lower is installed, and untrusted users can register as subscribers to access the vulnerable unserialize() call via the attachmentUrl parameter.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.1.0
Interim mitigation

Update the plugin to a patched version once available, or remove the plugin if no update exists. Additionally, audit the WordPress environment for other plugins/themes that could provide a POP chain, and consider restricting user registration to minimize the attack surface.

Recommended fix High confidence

Any version above 2.1.0 (check WordPress plugin repository for latest stable release)

  1. Check current plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Dashboard > Updates or check the plugin page for available updates
  3. Update Social Media Share Buttons to the latest available version (any version above 2.1.0 contains the fix)
  4. Alternatively, upload the latest version of the plugin from the WordPress plugin repository after update is released
  5. Test the plugin functionality after update to ensure the social share buttons work correctly
  6. Verify no breaking changes in your specific use case
Caveat Minimal risk - this is a security patch; test in staging if using custom configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Social Media Share Buttons 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 the upgrade done

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-2024-1685 — 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-1685 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