CVE-2026-15663
MediumCVSS 4.9Exploitation Probability (EPSS)
Low risk22th percentile - higher than 22% of all known CVEs
Summary
The Ninja Forms plugin for WordPress is vulnerable to generic SQL injection via import files. An authenticated attacker with admin privileges can append SQL queries to existing ones to extract sensitive data from the database.
Risk Assessment
An attacker with admin access can steal database contents, including passwords and user data.
Recommendation
Update the Ninja Forms plugin to version 3.14.10 or later.
Other vulnerabilities in Ninja Forms
See all- CVE-2026-65049Critical
The Ninja Forms plugin version 3.14.8 and prior for WordPress Multisite contains an incorrect authorization vulnerability that allows a subsite Administrator to trigger network-wide deletion of all Ninja Forms data. Attackers can send a crafted POST request to the admin-ajax.php endpoint with the nf_delete_all_data action and a per-site nonce to invoke migration routines that unconditionally iterate all blogs via switch_to_blog(), dropping all nf3_* tables and clearing options and transients across every subsite in the network without requiring super-admin or network-admin privileges.
- CVE-2026-65048Critical
The Ninja Forms plugin for WordPress versions 3.10.4 through 3.14.9 contains an unauthenticated stored cross-site scripting vulnerability in the Repeatable Fieldset feature. The parseSubmissionIndex() function accepts arbitrary strings as submission indexes without numeric validation, and admin_form_element() interpolates the index directly into HTML without escaping. An unauthenticated attacker can submit a public form with a crafted repeater child key containing malicious script payloads, which execute in an administrator's browser when viewing submissions in the WordPress admin panel.
- CVE-2019-10869High
The Ninja Forms plugin for WordPress before version 3.0.23 (when the Uploads add-on is activated) contains path traversal and unrestricted file upload vulnerabilities. This allows an attacker to traverse the file system to access files and execute code via the name and tmp_name parameters in includes/fields/upload.php.
- CVE-2026-15256Medium
The Ninja Forms WordPress plugin before 3.14.10 does not prevent user-supplied query-string input, used to pre-populate a form field's default value, from being processed as a shortcode, allowing unauthenticated attackers to execute arbitrary shortcodes registered on the site when a form so configured is embedded on a public page.
- CVE-2026-65052High
Ninja Forms WordPress plugin version 3.14.8 and earlier contains an improper input validation vulnerability. Unauthenticated attackers can inject arbitrary numeric values into form calculations and payment totals by submitting values that do not match any configured option in ListSelect or ListRadio fields. This can lead to manipulation of payment amounts, including setting them to zero.
- CVE-2026-65051Medium
Vulnerability in the Ninja Forms WordPress plugin version 3.14.8 allows unauthenticated attackers to bypass form validation by merging attacker-controlled field metadata before validation. Attackers can send a malicious AJAX request, overriding field types, removing required flags, and disabling CAPTCHA.
- CVE-2026-65050Medium
Vulnerability in the Ninja Forms WordPress plugin version 3.14.8 and earlier. Missing authorization in the Gutenberg block 'ninja-forms/submissions-table' allows authenticated attackers with Author role to expose stored form submissions (including PII) to unauthenticated visitors.
- CVE-2026-1239High
The Ninja Forms plugin for WordPress is vulnerable to unauthorized data access due to a missing authorization check on the 'ninja-forms-views/token/refresh' REST callback in all versions up to and including 3.14.1. This allows unauthenticated attackers to view form submissions, which may contain sensitive information.
Original NVD description (English source)
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.