dbcve.org
Slick Social Share ButtonsWordPress extension · Leechesnutt

CVE-2023-6878

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 2.4.11 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Slick Social Share Buttons plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'dcssb_ajax_update' function in versions up to, and including, 2.4.11. This makes it possible for authenticated attackers, with subscriber-level permissions or above to update the site options arbitrarily.

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 Slick Social Share Buttons WordPress plugin has a Broken Access Control vulnerability in the 'dcssb_ajax_update' function. The function lacks a capability check, allowing any authenticated user with subscriber-level permissions or higher to arbitrarily modify site options through the plugin's AJAX handler.

MitigationUpdate the plugin to version 2.4.12 or later which implements proper capability validation. If no patched version is available, disable the plugin or restrict user registrations until a fix is released.

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
Slick Social Share ButtonsWordPress extension
Affected:<= 2.4.11

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Slick Social Share Buttons'. Note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The plugin is installed and the version listed is 2.4.11 or lower.
  2. Confirm AJAX endpoint accessibility
    Check if the file containing 'dcssb_ajax_update' function exists in the plugin directory (typically in includes/ajax.php or similar). The function registers with wp_ajax_dcssb_ajax_update hook.
    Affected if The 'dcssb_ajax_update' function is present and registered as an AJAX action in the plugin code.
  3. Identify users with subscriber-level access
    In WordPress admin, go to Users > All Users. Review the role column for any accounts assigned Subscriber, Contributor, Author, or Editor roles.
    Affected if There is at least one user account with subscriber-level permissions or higher (these roles have lower privilege than administrator but can access the vulnerable AJAX handler).
  4. Check user registration settings
    In WordPress admin, go to Settings > General and verify if 'Membership' - 'Anyone can register' is enabled, and note the default new user role.
    Affected if User registration is open to the public, allowing anyone to create an account and gain subscriber-level access to the vulnerable AJAX function.

Your environment is affected if the Slick Social Share Buttons plugin version 2.4.11 or lower is installed, the dcssb_ajax_update AJAX handler is present, and any user with subscriber-level permissions (or the ability to obtain such permissions via open registration) exists in WordPress.

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.4.11
Interim mitigation

Update the plugin to version 2.4.12 or later which implements proper capability validation. If no patched version is available, disable the plugin or restrict user registrations until a fix is released.

Recommended fix Moderate confidence

Slick Social Share Buttons version 2.4.12 or later

  1. Update the Slick Social Share Buttons plugin to version 2.4.12 or later via the WordPress admin dashboard under Plugins > All Plugins > Slick Social Share Buttons > Update Now
  2. Alternatively, navigate to Dashboard > Updates and click 'Update Now' to update all plugins including this one
  3. Verify the update completed successfully by checking the plugin version in Plugins > Installed Plugins
  4. Confirm the vulnerability is remediated by verifying that subscriber-level users can no longer access the dcssb_ajax_update function

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

Fix this in Slick Social Share Buttons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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