Sassy Social ShareWordPress extension · Heateor
CVE-2024-11252
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 Sharing Plugin – Sassy Social Share plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the heateor_mastodon_share parameter in all versions up to, and including, 3.3.69 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 Sassy Social Share WordPress plugin versions up to 3.3.69 contain a reflected XSS vulnerability in the heateor_mastodon_share parameter. This parameter is not sanitized on input or escaped on output, allowing unauthenticated attackers to inject arbitrary JavaScript via malicious URLs. Successful exploitation requires social engineering to trick users into clicking crafted links.
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
Sassy Social ShareWordPress extension
< 3.3.70CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck for the presence of the Sassy Social Share plugin by looking for the directory /wp-content/plugins/sassy-social-share/ or checking the WordPress plugins admin pageAffected if The plugin directory or entry is not found - not applicable
-
Identify installed versionRead the main plugin file (usually sassy-social-share.php) and look for the Version header in the plugin comments, or check via WordPress admin under Plugins > Installed PluginsAffected if The displayed version number is less than 3.3.70 (for example 3.3.69, 3.3.68, etc.)
-
Check mastodon sharing feature statusReview plugin settings in WordPress admin under the Sassy Social Share configuration. Look for any Mastodon-related sharing options or buttons that may be enabled on the siteAffected if Mastodon sharing feature is enabled and the plugin version is vulnerable - the XSS can be triggered via the heateor_mastodon_share URL parameter
-
Inspect for vulnerable URL parameter handlingTest the site by submitting a request with the parameter heateor_mastodon_share=<script>alert(1)</script> to any page where the social share buttons appear, then examine if the parameter value is reflected unescaped in the HTML responseAffected if The parameter value appears literally (unescaped) in the page source - confirms the vulnerability is present and exploitable
If the Sassy Social Share plugin version is below 3.3.70 AND the mastodon sharing feature is active, the site is vulnerable to reflected XSS via the heateor_mastodon_share parameter.
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.
dbcve · scoped3.3.70
Update the Sassy Social Share plugin to version 3.3.70 or later. Review other plugin parameters for similar sanitization issues as a proactive measure.
3.3.70
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Sassy Social Share' in the plugin list
- Click 'Update Now' or 'Update' button to install version 3.3.70
- Alternatively, use WP-CLI: wp plugin update sassy-social-share --version=3.3.70
- Verify the plugin shows version 3.3.70 after update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Sassy Social Share
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-11252 — 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-11252 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