Safeguard
Vulnerability Analysis•

CVE-2021-4451: Medium PHAR Deserialization in NinjaFirewall

CVE-2021-4451 is an authenticated PHAR deserialization flaw in the NinjaFirewall WordPress plugin up to 4.3.3. Update to the fixed release from NinTechNet.

Safeguard Security Team
3 min read

CVE-2021-4451 is a medium severity (CVSS 6.6) authenticated PHAR deserialization flaw in the NinjaFirewall plugin for WordPress, in versions up to and including 4.3.3. It needs a privileged login. Update to the latest NinjaFirewall release and confirm the exact fixed version in the vendor notice.

What's affected

  • NinjaFirewall (WP Edition) for WordPress, versions up to and including 4.3.3, per the NVD record.
  • Requires an authenticated user with high privileges, which keeps the score at 6.6.
  • The record says the deserialization could enable other plugin or theme exploits if vulnerable software is present.
  • The vendor blog post listed in the record could not be retrieved, so we have not confirmed the first fixed version. Check it.
  • KEV status: false.

How to check if you're exposed

Check the installed version in the WordPress admin, or use WP-CLI.

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

Versions at 4.3.3 or lower are in range. Also review the list of administrator accounts, since the flaw needs a privileged user to reach it.

What to do now

  1. Update NinjaFirewall to the current release through the plugin screen.
  2. Read the vendor security notice to confirm the first fixed version and any extra steps.
  3. Audit administrator accounts and remove any you do not recognise, and enable two factor authentication for the rest.
  4. Update every other plugin and theme, because the record says the risk grows when other vulnerable software is installed.
  5. Review logs for unusual admin activity on the dates you were running an affected version.

Why it matters

The class is CWE-502, deserialization of untrusted data. A PHAR archive carries serialized metadata, and PHP can load that metadata as objects when a file operation touches a path using the phar scheme. The danger depends on which classes exist in the application, which is why the record warns about other plugins and themes.

It is easy to dismiss a bug that needs admin access. Two things argue against that. Admin credentials are stolen and reused often, and a security plugin is a poor place to leave a gap, since attackers tend to look closely at the tools meant to protect a site.

Try it yourself

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

Quick check

Do I need to worry if I trust all my admins?

The risk is lower, but admin accounts can be phished or reused. Updating is quick and removes the question.

Which version fixes it?

The record only gives the affected range, up to 4.3.3. Check the NinTechNet notice 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.