dbcve.org
Social RocketWordPress extension · Wpsocialrocket

CVE-2024-37258

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 1.3.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Social Rocket allows Reflected XSS.This issue affects Social Rocket: from n/a through 1.3.3.

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

Reflected XSS vulnerability in Social Rocket plugin allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected back in web pages. The vulnerability affects versions up to and including 1.3.3.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied data before reflecting it in HTML pages to prevent script injection.

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 RocketWordPress extension
Affected:< 1.3.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Social Rocket plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'social-rocket' or similar
    Affected if The Social Rocket plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > click on Social Rocket details, or check the plugin's main PHP file for a 'Version' header in the plugin comment block
    Affected if The version number is 1.3.3 or lower (anything below 1.3.4)
  3. Identify reflected input points
    Review the plugin code for PHP variables that accept user input (like $_GET, $_POST, $_REQUEST) and are directly output to HTML without sanitization functions such as esc_html(), esc_attr(), or wp_kses()
    Affected if User-supplied parameters are reflected in page output without proper escaping
  4. Check for malicious requests in access logs
    Search web server access logs (Apache/Nginx) for requests to pages using the Social Rocket plugin containing suspicious script tags or javascript: URIs in query parameters
    Affected if Evidence of script injection attempts targeting the plugin's reflected parameters exists in logs

A user is affected if the Social Rocket plugin version is 1.3.3 or lower and the plugin handles user input that gets reflected in HTML pages without sanitization.

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.3.4 or later
Fixed in 1.3.4
Interim mitigation

Implement proper input validation and output encoding/escaping for all user-supplied data before reflecting it in HTML pages to prevent script injection.

Recommended fix Moderate confidence

Social Rocket version 1.3.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Social Rocket plugin
  4. Check if the current version is below 1.3.4
  5. If update available, click 'Update Now' to upgrade to version 1.3.4
  6. Alternatively, navigate to Dashboard > Updates and apply available updates
  7. Verify the plugin is now running version 1.3.4 after update completes

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

Fix this in Social Rocket 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-37258 — 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-37258 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