LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6878: Slick Social Share Buttons <= 2.4.11 - Authenticated (Subscriber+) Arbitrary Option Update

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A logged-in WordPress user with Subscriber-level access could change site options through Slick Social Share Buttons. Site options control important behavior, so abuse could affect confidentiality, integrity, or availability. The issue is rated high and applies to plugin versions up to and including 2.4.11.

Executive priority

Treat as high priority for affected WordPress properties, especially customer-facing sites with user accounts. The attacker does not need administrator access, and arbitrary option changes can create broad business impact. Prioritize inventory, containment, and vendor guidance review.

Technical view

CVE-2023-6878 is a missing authorization check, CWE-285, in the plugin's dcssb_ajax_update function. Authenticated users with Subscriber privileges or higher can arbitrarily update WordPress site options. The CVSS 3.1 score is 8.8 with network access, low complexity, low privileges, and no user interaction.

Likely exposure

Exposure is limited to WordPress sites running Slick Social Share Buttons versions up to 2.4.11, especially sites allowing untrusted or many low-privilege accounts. The provided affected metadata is sparse, so confirm installed plugin name and version directly.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires a valid WordPress account, but only Subscriber-level permissions are needed. The impact depends on which site options an attacker changes.

Researcher notes

The core issue is authorization failure in dcssb_ajax_update, referenced in the 2.4.11 plugin source. Do not assume a patched version from this bundle; it names affected versions through 2.4.11 but does not provide a confirmed remediation release.

Mitigation direction

  • Inventory WordPress sites for Slick Social Share Buttons installations.
  • If version is 2.4.11 or older, check vendor guidance immediately.
  • Disable or remove the plugin where no fixed release is available.
  • Limit untrusted Subscriber-level accounts until remediation is complete.
  • Review WordPress option integrity after suspected exposure.

Validation and detection

  • Confirm plugin slug and installed version on each WordPress site.
  • Identify whether public registration or low-privilege user creation is enabled.
  • Review logs for suspicious authenticated AJAX activity.
  • Check for unexpected recent changes to WordPress site options.
  • Track Wordfence, CVE, and WordPress plugin sources for fix status.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6878 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-6878Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
remix4Slick Social Share Buttons0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-285 · source CWE mapping

Improper Authorization

Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.