Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit form with serialized payload
-
DeliveryPayload stored in submission (unauthenticated)
-
ExploitAdmin exports submissions to CSV
-
ExecutionValue deserialized triggering POP chain
-
ImpactFile operations or RCE on server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the Ninja Forms plugin version 3.15.3, which deserializes user-submitted form field values during the administrator CSV export of form submissions. The attacker's payload can be planted unauthenticated by anyone able to submit a form (PR:N), but the deserialization sink only fires when an administrator later performs the 'export submissions to CSV' action (UI:R). Achieving arbitrary file operations or remote code execution additionally depends on a suitable POP (property-oriented programming) gadget chain being present in another installed plugin or theme - without such a chain the object injection has limited practical impact. These two gates (admin-initiated export plus an available POP chain in the co-installed extension stack) are the primary factors limiting real-world exploitation. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.5) describes an unauthenticated network-reachable flaw whose full C:H/I:H/A:H impact is explicitly conditional - the description states RCE/file operations occur only 'if a suitable POP chain is present via another installed plugin or theme.' That conditionality is correctly reflected in AC:H and is the single most important risk qualifier: without a usable POP gadget chain in the co-installed plugin/theme stack, the primary object-injection sink yields limited or no impact. Exploitation also requires UI:R - an administrator must actively export form submissions to CSV to trigger deserialization - so this is not a fire-and-forget remote exploit despite the network vector. A public exploit exists (WPScan), but there is no CISA KEV listing and no EPSS score in the provided data, so there is no evidence of active or automated exploitation; treat POC availability and active exploitation as distinct signals. Net: a genuine, high-value bug on a very widely deployed plugin, but real-world exploitability is gated by (1) presence of a POP chain and (2) an admin performing the export. Missing data to flag explicitly: CWE is 'N/A' in the input though this is unambiguously a deserialization/PHP Object Injection class (CWE-502/CWE-915); EPSS and KEV status are absent (absence is not evidence of low risk, merely unmeasured); CPE vendor is recorded as 'unknown' rather than the actual maintainer (Saturday Drive). |
| Exploit ScenarioDerived | An unauthenticated attacker submits a Ninja Forms form on a victim WordPress site, placing a crafted serialized PHP object payload into a form field value, which is stored with the submission. Later, an administrator exports the collected submissions to CSV, at which point the stored value is deserialized; if a POP gadget chain exists in another installed plugin or theme, this drives arbitrary file operations or remote code execution. A public exploit for this vulnerability is available via WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
PHP Object Injection in the Ninja Forms WordPress plugin 3.15.3 allows unauthenticated attackers to plant serialized payloads in user-submitted form field values that are later deserialized when an administrator exports submissions to CSV. Publicly available exploit code exists, but full impact - arbitrary file operations or remote code execution - is conditional on a suitable POP gadget chain being present in another installed plugin or theme; without such a chain, the object injection has limited practical impact. The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H (7.5) reflects the admin-initiated export action and POP-chain prerequisites rather than guaranteed code execution.
RemediationAI
No vendor-released patch or fixed version is identified in the provided intelligence at time of analysis. Monitor the WPScan advisory at https://wpscan.com/vulnerability/7b279db2-92e0-4122-b5c6-aa12b7b01858/ and Ninja Forms vendor channels for a patched release, and update Ninja Forms beyond 3.15.3 once a fixed version is available. If immediate patching is not possible, consider temporarily disabling or removing the Ninja Forms plugin on sites that do not need it, with the trade-off of losing all form functionality. If the plugin must remain active, restrict form submissions to authenticated or trusted users where feasible (reduces the unauthenticated PR:N entry point but may break public-facing forms); disable or restrict the CSV export submissions feature if it can be done without breaking required reporting (loses administrative export capability); and reduce the available gadget-chain surface by removing unused plugins and themes from the WordPress stack (may affect site features). Enforce least privilege on administrator accounts and monitor or alert on export actions, though these are detective controls and do not prevent the underlying object injection. A WAF rule blocking serialized PHP object patterns in form submissions can provide virtual patching, with potential false positives on legitimate serialized data.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Ninja Forms is a WordPress plugin that stores user-submitted form data in WordPress database tables. The flaw is in its CSV export functionality: when an administrator exports submissions, values originally submitted by users are passed to a PHP deserialization routine without adequate validation or integrity checking, creating a PHP Object Injection sink. The CPE string cpe:2.3:a:unknown:ninja_forms:*:*:*:*:*:*:*:* identifies the affected product family but uses an unknown vendor and wildcard version; the description specifically names version 3.15.3. Insecure deserialization, commonly mapped to CWE-502 although the CVE record lists CWE N/A, lets an attacker inject serialized PHP objects into form fields. Because exploitation for arbitrary file operations or RCE depends on magic methods and gadget chains available in co-installed WordPress plugins or themes, the assessed vector uses AC:H and UI:R: the unauthenticated attacker can submit the payload (PR:N), but an administrator must later trigger the export, and a suitable POP chain must exist in the site's plugin or theme stack. Public exploit code is reported, but no CISA KEV status is provided.
Know when Ninja Forms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated payload injection (PR:N) over the network, but AC:H (requires an external POP chain) and UI:R (admin must run CSV export); full C/I/A:H reflects potential RCE via the gadget chain.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Ninja Forms WordPress plugin 3.15.3 does not prevent user-submitted form field values from being deserialised when an administrator later exports form submissions to CSV, allowing unauthenticated attackers to perform PHP Object Injection; if a suitable POP chain is present via another installed plugin or theme, this can lead to actions such as arbitrary file operations or remote code execution.
Articles & Coverage 1
Technical POC Analysis
CWE-502 (Deserialization of Untrusted Data), surfaced by WPScan as "OBJECT INJECTION" / OWASP A8 Insecure Deserialization.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The Ninja Forms WordPress plugin version 3.15.3 contains a high-severity PHP object injection vulnerability (CVE-2026-91827) that allows unauthenticated attackers to plant malicious serialized payloads in form submissions, which are later deserialized when an administrator exports submissions to CSV. Publicly available exploit code exists, and successful exploitation could lead to arbitrary file operations or remote code execution if a suitable POP gadget chain is present in another installed plugin or theme. Organizations using this plugin are at risk of site compromise, data theft, or full server takeover, though exploitation requires an administrator to trigger the export and a specific gadget chain to be present.
No vendor-released patch identified at time of analysis; interim mitigations include restricting admin access, disabling CSV export or the plugin, deploying WAF rules to block serialized payloads, auditing for POP gadget chains, and monitoring admin export activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Ninja Forms
View allThe Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
Stored cross-site scripting in the Ninja Forms WordPress plugin 3.15.3 lets an unauthenticated visitor plant a script pa
The AJAX action, wp_ajax_ninja_forms_sendwp_remote_install_handler, did not have a capability check on it, nor did it ha
The Ninja Forms plugin before 3.3.14.1 for WordPress allows CSV injection. Rated high severity (CVSS 8.6), this vulnerab
The Ninja Forms Contact Form WordPress plugin before 3.6.13 unserialises the content of an imported file, which could le
The Ninja Forms Contact Form WordPress plugin before 3.6.4 does not escape keys of the fields POST parameter, which coul
The Ninja Forms WordPress plugin is vulnerable to sensitive information disclosure via the bulk_export_submissions funct
The Ninja Forms WordPress plugin before 3.8.11 does not escape an URL before outputting it back in an attribute, leading
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
The Ninja Forms Contact Form WordPress plugin before 3.6.22 does not properly escape user input before outputting it bac
In the Ninja Forms Contact Form WordPress plugin before 3.4.34, the wp_ajax_nf_oauth_connect AJAX action was vulnerable
An open redirect in the Ninja Forms plugin before 3.3.19.1 for WordPress allows Remote Attackers to redirect a user via
EUVD-2026-84283
GHSA-jvgp-rj42-qjww
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB