Is sassy-social-share (WordPress plugin) vulnerable?

WordPress sassy-social-share has 10 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

10advisories
0critical
0on CISA KEV
3no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-4971The Sassy Social Share plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'urls' parameter called via the 'heateormedium6.1<=3.3.3–
CVE-2021-24746The Social Sharing Plugin WordPress plugin before 3.3.40 does not escape the viewed post URL before outputting it back in onclick attributesmedium6.1<3.3.403.3.40
CVE-2021-39321Version 3.3.23 of the Sassy Social Share WordPress plugin is vulnerable to PHP Object Injection via the wp_ajax_heateor_sss_import_config AJhigh8.8=3.3.23–
CVE-2024-11252The Social Sharing Plugin – Sassy Social Share plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the heateor_mastodonmedium6.1<3.3.703.3.70
CVE-2024-1989The Social Sharing Plugin – Sassy Social Share plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'Sassy_Socmedium6.4<3.3.593.3.59
CVE-2024-2159The Social Sharing Plugin WordPress plugin before 3.3.61 does not validate and escape some of its shortcode attributes before outputting thmedium4.7<3.3.613.3.61
CVE-2022-4451The Social Sharing WordPress plugin before 3.3.45 does not validate and escape some of its shortcode attributes before outputting them back medium5.4<3.3.453.3.45
CVE-2024-1448The Social Sharing Plugin – Sassy Social Share plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(medium6.4<=3.3.56–
CVE-2024-4924The Social Sharing Plugin WordPress plugin before 3.3.63 does not sanitise and escape some of its settings, which could allow high privilegmedium6.1<3.6.33.6.3
CVE-2025-5528The Social Sharing Plugin – Sassy Social Share plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the heateor_mastodonmedium6.1<3.3.763.3.76

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.