CVE-2026-91827

7.5

WordPress · Ninja Forms

The Ninja Forms WordPress plugin contains a deserialization vulnerability that allows unauthenticated attackers to trigger PHP Object Injection during administrative CSV exports.

Executive summary

A critical deserialization vulnerability in the Ninja Forms plugin for WordPress allows unauthenticated attackers to execute arbitrary code or perform unauthorized file operations.

Vulnerability

This flaw involves the deserialization of untrusted user-submitted form data (CWE-502). An unauthenticated attacker can inject malicious serialized objects that are subsequently processed when an administrator exports form submissions to a CSV file.

Business impact

The vulnerability carries a CVSS score of 7.5, indicating a high risk to organizational security. Successful exploitation could lead to full system compromise, unauthorized data access, or the destruction of sensitive information stored within the WordPress environment. Given that the attack can be initiated by an unauthenticated user, the potential for widespread impact on the integrity and availability of business operations is significant.

Remediation

Immediate Action: Update the Ninja Forms plugin to version 3.15.4 or later immediately to resolve the deserialization flaw.

Proactive Monitoring: Monitor server logs for unusual PHP error messages or unexpected file access patterns following administrative CSV export tasks.

Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to block suspicious serialized PHP object patterns in HTTP requests.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

The severity of this vulnerability necessitates immediate attention, as it allows unauthenticated actors to target backend administrative functions. Administrators should verify their current version of Ninja Forms and apply the 3.15.4 patch without delay. If an immediate update is not feasible, administrators should restrict access to form export functions or consider temporarily disabling the plugin to prevent potential exploitation.

More WordPress CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Karthik Ramakrishnan, with WPScan (coordinator), per the CVE Program record.