Is social-warfare (WordPress plugin) vulnerable?

WordPress social-warfare has 5 known advisories in the phpwarden feed, 1 actively exploited. Feed 2026.10.29.1, updated 2026-10-28.

5advisories
1critical
1on CISA KEV
2no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-9978 KEVThe social-warfare plugin before 3.5.3 for WordPress has stored XSS via the wp-admin/admin-post.php?swp_debug=load_options swp_url parametermedium6.1<3.5.33.5.3
CVE-2021-4434The Social Warfare plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 3.5.2 via the 'swp_url' parcritical10.0<3.5.33.5.3
CVE-2023-0402The Social Warfare plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on several AJAX actions in vmedium5.4<=4.3.0–
CVE-2023-4842The Social Sharing Plugin - Social Warfare plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'social_warfare' shortcode medium6.4<=4.4.3–
CVE-2023-0403The Social Warfare plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.3.1. This is due to medium5.4<4.4.04.4.0

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.

# one-time install
pip install phpwarden

# then
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.