fixnx
mediumCVE-2026-15663

Ninja Forms <= 3.14.9 - Authenticated (Administrator+) SQL Injection via Import File 'settings' Key

The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to generic SQL Injection via Import File 'settings' Key in all versions up to, and including, 3.14.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerable keys originate from the 'settings' object in an attacker-controlled import file processed via file_get_contents() or base64-decoded/JSON-decoded blobs, bypassing wp_magic_quotes protections entirely; two distinct sinks are affected — _save_setting() in Model.php and insert_form_meta() in ImportForm.php — as only the value side is escaped while the key side receives no sanitization or parameterization at any point in the call chain.

Browse WordPress security risks
ProductNinja Forms – The Contact Form Builder That Grows With You
CVSS4.9
EPSSNot scored yet
UpdatedJuly 24, 2026

Quick answer

kstover Ninja Forms – The Contact Form Builder That Grows With You should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <= 3.14.9
  • up to and including 3.14.9

Fixed versions

  • 3.14.10

How to fix it

CVE-2026-15663 affects Ninja Forms – The Contact Form Builder That Grows With You and involves SQL injection. Successful exploitation may let an attacker read or change database data through the affected request path. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade Ninja Forms – The Contact Form Builder That Grows With You to 3.14.10 or a later vendor-supported fixed release.

  1. Inventory every deployment, device, package, plugin, container, build, and environment that uses Ninja Forms – The Contact Form Builder That Grows With You.
  2. Compare the installed version with the recorded affected range: <= 3.14.9, *-3.14.9.
  3. Upgrade Ninja Forms – The Contact Form Builder That Grows With You to 3.14.10 or a later vendor-supported fixed release.
  4. Until patched, disable the affected Ninja Forms – The Contact Form Builder That Grows With You feature or plugin and restrict its public and administrator endpoints.
  5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to Ninja Forms – The Contact Form Builder That Grows With You; remove access that is not required.
  6. Review web, database, WAF, and application logs for unusual query errors, delays, data access, or requests to the affected parameter.
  7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-15663 in place.
  • Use a safe regression test to confirm the affected SQL injection path no longer produces the vulnerable behavior.
  • Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
  • Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
  • Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

WordPressPHPSQL InjectionInformation Disclosure

Related security risks

More published guidance from the same primary category.

critical

SAML Single Sign On <= 5.4.4 - Unauthenticated Authentication Bypass via SAMLResponse Parameter

Updated July 24, 2026

medium

Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter

Updated July 24, 2026

medium

Kirki <= 6.0.14 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'context' Parameter

Updated July 24, 2026

Trusted references

Source advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceWordfence advisoryNVD, WordfenceWordfence advisoryNVD, Wordfence

FAQ

What is affected by CVE-2026-15663?

kstover Ninja Forms – The Contact Form Builder That Grows With You versions listed as affected should be reviewed: <= 3.14.9, up to and including 3.14.9.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.