WordPress security changelog
MEDIUM CVE-2021-4451 Analyzed

NinjaFirewall: Code execution

NinjaFirewall is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 6.6 CVSS 3.1 · security@wordfence.com
NVD score 7.2 CVSS 3.1 · nvd@nist.gov
Component
NinjaFirewall
Plugin slug
ninjafirewall
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 16, 2024
Weakness
CWE-502 — Deserialization of Untrusted Data

This CVE was published Oct 16, 2024 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update NinjaFirewall to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The NinjaFirewall plugin for WordPress is vulnerable to Authenticated PHAR Deserialization in versions up to, and including, 4.3.3. This allows authenticated attackers to perform phar deserialization on the server. This deserialization can allow other plugin or theme exploits if vulnerable software is present (WordPress, and NinjaFirewall).

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

NVD vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Primary and upstream sources