CVE-2026-11363: Ninja Forms <= 3.14.6 - Authenticated (Administrator+) PHP Object Injection via Form Import

Published Sep 9, 2026
·
Updated

The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.6 via deserialization of untrusted input . This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. The deserialization is triggered automatically during form import when WPNHelper::buildnfcache() invokes $action->getsettings() immediately after the crafted form is imported, requiring no further interaction beyond the import action itself.

Affected Software

1 affected component
Ninja Forms Ninja Forms – The Contact Form Builder That Grows With You<=3.14.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Ninja Forms – The Contact Form Builder That Grows With You (WordPress plugin) to a version that resolves this vulnerability.

    Fixed in 3.14.6

Event History

Sep 9, 2026
CVE Published
via MITRE·03:28 AM
Data Sourced
via MITRE·03:28 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can realistically exploit this issue?

An attacker must already be authenticated with administrator-level access or higher in WordPress. The attack is performed by importing a crafted Ninja Forms form.

2

Is a vulnerable Ninja Forms installation alone enough to cause impact?

No. Ninja Forms has no known usable POP chain, so exploitation has no impact unless another installed plugin or theme provides a POP chain. The possible outcome depends on that chain and can include arbitrary file deletion, sensitive-data retrieval, or code execution.

3

Does exploitation require a separate action after the malicious form is imported?

No. Deserialization is triggered automatically as part of the form-import process when the imported form's settings are processed.

4

How can I determine whether the installed version is affected?

All Ninja Forms versions through 3.14.6, including 3.14.6, are affected according to the available information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203