Safeguard
Vulnerability Analysis•

CVE-2021-4434: Critical Code Injection in Social Warfare Plugin

CVE-2021-4434 is a critical (CVSS 10.0) remote code execution flaw in the Social Warfare WordPress plugin up to 3.5.2. Update the plugin or remove it.

Safeguard Security Team
3 min read

CVE-2021-4434 is a critical (CVSS 10.0) remote code execution flaw in the Social Warfare plugin for WordPress, in versions up to and including 3.5.2, through the swp_url parameter. Update to the current release from the plugin author. Check the advisory for the exact fixed version.

What's affected

  • Social Warfare for WordPress, versions up to and including 3.5.2, per the NVD record.
  • The record gives CVSS 10.0 with no privileges and no user interaction required, with a changed scope.
  • The Wordfence page listed in the record could not be retrieved, so we cannot confirm the exact first fixed version here. Check the plugin changelog and the Wordfence entry.
  • KEV status: false in the record, and nothing we retrieved reports exploitation in the wild.

How to check if you're exposed

From the WordPress admin, open Plugins and read the version next to Social Warfare. With shell access, WP-CLI can list it.

wp plugin list --fields=name,status,version

Anything at 3.5.2 or lower is in the affected range. Inactive plugins still sit on disk, so remove ones you do not use rather than leaving them deactivated.

What to do now

  1. Update Social Warfare to the latest release through the WordPress dashboard or wp plugin update social-warfare.
  2. If you do not need the plugin, delete it instead of updating.
  3. Check the site for unexpected PHP files, new administrator accounts and modified plugin or theme files, because a code execution bug may have been used before you patched.
  4. Rotate WordPress salts, database credentials and any API keys stored on the server if you find signs of tampering.
  5. Turn on automatic updates for plugins you intend to keep.

Why it matters

The class is CWE-94, improper control of generation of code. In plain terms, a value that should have been treated as data was able to influence code that the server then ran. The record names the swp_url parameter as the route, which means an attacker could send a crafted request without logging in.

Plugins like this one sit on a large number of public sites, which makes unauthenticated flaws attractive to anyone scanning at scale. The practical lesson is to keep a list of installed plugins and their versions, and to delete what you are not using.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does this need a login?

The CVSS vector in the record says no privileges are required, so the flaw can be reached without an account.

What is the fixed version?

The record only says versions up to and including 3.5.2 are affected. Check the plugin changelog or the Wordfence entry for the first fixed release.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.