dbcve.org
Social Media Share Buttons \& Social Sharing IconsWordPress extension · Inisev

CVE-2024-37552

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to 2.9.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Inisev Social Media & Share Icons allows Stored XSS.This issue affects Social Media & Share Icons: from n/a through 2.9.1.

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

Stored XSS vulnerability in the Inisev Social Media & Share Icons WordPress plugin allows attackers to inject malicious JavaScript through unsanitized input, which is then stored and executed when other users view affected pages.

MitigationUpdate the plugin to the latest patched version once available, or temporarily disable the plugin. Implement additional input sanitization and consider deploying a WAF rule to detect XSS 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
Social Media Share Buttons \& Social Sharing IconsWordPress extension
Affected:< 2.9.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Inisev plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Inisev Social Media' or 'Social Media Share Buttons' in the plugin list
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins page, click on the plugin to view its details, or inspect the plugin header comment in wp-content/plugins/inisev-social-media/inisev-social-media.php to find the Version field
    Affected if The displayed version number is less than 2.9.2 (for example, 2.9.1, 2.9.0, or earlier)
  3. Identify plugin admin settings pages
    Navigate through the WordPress admin menu looking for Inisev plugin pages (typically under Settings or a dedicated Inisev menu item) where social media accounts or share button configurations can be saved
    Affected if Plugin settings pages exist and accept user input for social media usernames, URLs, or button configurations
  4. Inspect stored plugin data in database
    Use phpMyAdmin or WP-CLI to query the wp_options table for option_name values containing 'inisev' or the plugin prefix; examine any stored values that accept user input such as usernames, profile URLs, or custom messages
    Affected if Database contains plugin options with unsanitized user-supplied content that could contain script tags
  5. Review page source for injected scripts
    Visit pages where Inisev share buttons are displayed, view the page source (right-click > View Page Source), and search for script tags or event handlers (onclick, onerror, onload) that originate from plugin output
    Affected if Unexpected script tags or JavaScript event handlers appear in the HTML output surrounding the share buttons

A defender is affected if the Inisev Social Media Share Buttons plugin is installed and the installed version is lower than 2.9.2, with user-configurable input fields present in the plugin settings.

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

Update the plugin to the latest patched version once available, or temporarily disable the plugin. Implement additional input sanitization and consider deploying a WAF rule to detect XSS attempts.

Recommended fix High confidence

Social Media Share Buttons & Social Sharing Icons version 2.9.2

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Log in to the WordPress admin dashboard.
  3. 3. Navigate to Plugins > Installed Plugins.
  4. 4. Find 'Social Media Share Buttons & Social Sharing Icons' (by Inisev).
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.9.2.
  6. 6. Alternatively, download version 2.9.2 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version shows 2.9.2 in the plugins list.
  8. 8. Clear any caching plugins and test that the social share functionality works correctly.

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

Fix this in Social Media Share Buttons \& Social Sharing Icons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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