Social RocketWordPress extension · Wpsocialrocket
CVE-2024-9702
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 · uneditedThe Social Rocket – Social Sharing Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'socialrocket-floating' shortcode in all versions up to, and including, 1.3.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe Social Rocket WordPress plugin versions up to 1.3.4 contain a Stored Cross-Site Scripting vulnerability in the 'socialrocket-floating' shortcode. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through unsanitized user-supplied attributes in the shortcode, which executes when other users view the compromised pages.
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
<= 1.3.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Social Rocket plugin versionNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'Social Rocket' (or 'Wpsocialrocket Social Rocket'), and read the version number displayedAffected if The installed version is 1.3.4 or lower
-
Identify use of the vulnerable shortcodeSearch your WordPress database or content for the '[socialrocket-floating]' shortcode string. This can be done via plugin search tools, directly querying the wp_posts table, or using a site search featureAffected if The shortcode [socialrocket-floating] exists in any post, page, or custom post type content
-
Inspect shortcode attributes for unsanitized inputView the source HTML or inspect elements on pages containing the socialrocket-floating shortcode. Examine the rendered anchor tags and look for suspicious attributes such as javascript: URIs, script tags embedded in attribute values, or HTML event handlers like onerror, onload, onclickAffected if The shortcode attributes contain unescaped HTML, JavaScript code, or event handlers that were not sanitized before rendering
-
Review contributor-level user accountsGo to Users > All Users in the WordPress admin and identify any accounts with the Contributor role. These users have the permission level required to exploit this vulnerabilityAffected if There are one or more Contributor-level users who could have authored malicious shortcode content
You are affected if the Social Rocket plugin version is 1.3.4 or lower AND the socialrocket-floating shortcode is present in your content with unsanitized user-supplied attributes.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Social Rocket plugin to version 1.3.5 or later, which contains proper input sanitization and output escaping. If no update is available, remove or disable the 'socialrocket-floating' shortcode until a patch is released.
Fix this in Social Rocket
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9702 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9702 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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