Sassy Social ShareWordPress extension · Heateor
CVE-2025-5528
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.75 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.75 fail to sanitize and escape the heateor_mastodon_share parameter before outputting it in the response, allowing unauthenticated attackers to inject arbitrary JavaScript via reflected XSS. Successful exploitation requires tricking a user into clicking a maliciously crafted link.
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.76CVSS 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 Sassy Social Share plugin is installedCheck the WordPress plugins directory for the heateor-sassy-social-share folder, or list active plugins via WP-CLI: wp plugin list --name='sassy-social-share'Affected if Plugin is installed and active
-
Identify the installed plugin versionRead the main plugin file (usually heateor-sassy-social-share.php) and locate the 'Version' header in the plugin comments, or use: wp plugin get heateor-sassy-social-share --field=versionAffected if Version is less than 3.3.76
-
Inspect the vulnerable parameter handlingExamine the plugin file handling the heateor_mastodon_share parameter (typically in the main plugin PHP file), searching for code that outputs this parameter without sanitization using functions like echo, print, or printfAffected if Code outputs heateor_mastodon_share directly without esc_html, esc_attr, or similar escaping functions
-
Test for reflected XSS vulnerabilitySend a crafted request with a test payload in the heateor_mastodon_share parameter (e.g., ?heateor_mastodon_share=<script>alert(1)</script>) and inspect the response to see if the payload is reflected unescapedAffected if The payload appears in the response HTML without being escaped or neutralized
-
Check server access logs for exploitation attemptsReview web server access logs for requests containing heateor_mastodon_share parameter with suspicious patterns like <script>, javascript:, or event handlersAffected if Log entries show unauthenticated requests with XSS payloads in this parameter
If the Sassy Social Share plugin version is below 3.3.76 and the heateor_mastodon_share parameter is reflected in responses without escaping, the environment is vulnerable to CVE-2025-5528.
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.76
Update the Sassy Social Share plugin to version 3.3.76 or later which includes proper input sanitization and output escaping for the affected parameter.
Sassy Social Share version 3.3.76
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Sassy Social Share plugin in the list
- If an update is available, click 'Update Now' to upgrade to version 3.3.76
- Alternatively, deactivate the current version and reinstall version 3.3.76 from the WordPress plugin repository
- Verify the plugin shows version 3.3.76 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
- 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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5528 — 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-2025-5528 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