dbcve.org
SliderWordPress extension · Supsystic

CVE-2024-47330

HIGH · 8.8 CVSS v3.1 Published 2024-09-26
Fix available
A fix is available. Upgrade to 1.8.7 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
Missing Authorization vulnerability in Supsystic Slider by Supsystic, Supsystic Social Share Buttons by Supsystic.This issue affects Slider by Supsystic: from n/a through 1.8.6; Social Share Buttons by Supsystic: from n/a through 2.2.9.

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

Missing authorization vulnerability in two Supsystic WordPress plugins (Slider and Social Share Buttons). The vulnerability allows unauthenticated or unauthorized users to access functionality they should not have access to, likely due to missing capability checks or nonce verification on sensitive AJAX endpoints or admin actions.

MitigationUpdate to the latest versions of both Supsystic Slider and Social Share Buttons plugins once patches are released. Until then, consider disabling the plugins or implementing a web application firewall to block unauthorized access attempts.

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
SliderWordPress extension
Affected:< 1.8.7
Social Share ButtonsWordPress extension
Affected:<= 2.2.9

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. Check Supsystic Slider plugin version
    Navigate to WordPress admin dashboard > Plugins > Supsystic Slider and view the version number, or check the plugin header in wp-content/plugins/slider-by-supsystic/main.php
    Affected if Version is present and less than 1.8.7
  2. Check Supsystic Social Share Buttons plugin version
    Navigate to WordPress admin dashboard > Plugins > Social Share Buttons by Supsystic and view the version number, or check the plugin header in wp-content/plugins/social-share-buttons-by-supsystic/main.php
    Affected if Version is present and less than or equal to 2.2.9
  3. Identify if both plugins are active
    Run SQL query: SELECT option_value FROM wp_options WHERE option_name IN ('active_plugins') AND option_value LIKE '%slider-by-supsystic%' OR option_value LIKE '%social-share-buttons-by-supsystic%'; or inspect plugin list in WordPress admin
    Affected if Either or both plugins appear in active plugins list
  4. Check for unauthorized AJAX endpoint access
    Test accessing common Supsystic AJAX endpoints without authentication (e.g., ?action=supsystic_slider_ajax or ?action=supsystic_social_ajax) and observe if the server returns a 200 response with data instead of requiring login
    Affected if AJAX endpoints return valid data or privileged responses without requiring authentication or capability verification

If either Supsystic Slider version < 1.8.7 or Social Share Buttons version <= 2.2.9 is installed and active, the missing authorization vulnerability is present regardless of specific configurations.

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 1.8.7 or later
Fixed in 1.8.7
Interim mitigation

Update to the latest versions of both Supsystic Slider and Social Share Buttons plugins once patches are released. Until then, consider disabling the plugins or implementing a web application firewall to block unauthorized access attempts.

Recommended fix Moderate confidence

Slider by Supsystic: upgrade to 1.8.7 or later; Social Share Buttons by Supsystic: upgrade to version greater than 2.2.9 (check vendor for specific fixed release)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Locate 'Slider by Supsystic' and check if current version is below 1.8.7
  4. 4. If vulnerable, click 'Update Now' to install version 1.8.7 or later
  5. 5. Verify the update was successful by checking the plugin version
  6. 6. Test the slider functionality on your site to ensure it works correctly
  7. 7. For 'Social Share Buttons by Supsystic', check if a newer version is available that addresses CVE-2024-47330; update to the latest version if available
Caveat Standard minor/patch upgrades typically have no breaking changes; test in staging if concerned

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

Fix this in Slider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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