Ninjaforms vulnerabilities

64 vulnerabilities

Known vulnerabilities in Ninjaforms products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 5 products.

Products

5
8.6CVE-2018-16308ninjaformsninja_forms+1
EPSS score
1.79%
The Ninja Forms plugin before 3.3.14.1 for WordPress allows CSV injection.
6.1CVE-2018-19796ninjaformsninja_forms+1
EPSS score
1.58%
An open redirect in the Ninja Forms plugin before 3.3.19.1 for WordPress allows Remote Attackers to redirect a user via the lib/StepProcessing/step-processing.php (aka submissions download page) redirect parameter.
9.1CVE-2018-20981ninjaformsninja_forms+1
EPSS score
1.74%
The ninja-forms plugin before 3.3.9 for WordPress has insufficient restrictions on submission-data retrieval during Export Personal Data requests.
7.5CVE-2018-20980ninjaformsninja_forms+1
EPSS score
1.39%
The ninja-forms plugin before 3.2.15 for WordPress has parameter tampering.
6.1CVE-2018-7280ninjaformsninja_forms+1
EPSS score
0.76%
The Ninja Forms plugin before 3.2.14 for WordPress has XSS.
5.5CVE-2021-36827ninjaformsninja_forms+2
EPSS score
0.52%
Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Saturday Drive's Ninja Forms Contact Form plugin <= 3.6.9 at WordPress via "label".
5.5CVE-2021-25066ninjaformsninja_forms+2
EPSS score
0.59%
The Ninja Forms Contact Form WordPress plugin before 3.6.10 does not sanitize and escape some imported data, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.
4.8CVE-2021-25056ninjaformsninja_forms+2
EPSS score
0.59%
The Ninja Forms Contact Form WordPress plugin before 3.6.10 does not sanitise and escape field labels, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.
4.8CVE-2021-24381ninjaformscontact_form+2
EPSS score
0.62%
The Ninja Forms Contact Form WordPress plugin before 3.5.8.2 does not sanitise and escape the custom class name of the form field created, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.
5.8CVE-2021-24166ninjaformsninja_forms+2
EPSS score
0.46%
The wp_ajax_nf_oauth_disconnect from the Ninja Forms Contact Form – The Drag and Drop Form Builder for WordPress WordPress plugin before 3.4.34 had no nonce protection making it possible for attackers to craft a request to disconnect a site's OAuth connection.
8.8CVE-2021-24163ninjaformsninja_forms+2
EPSS score
1.44%
The AJAX action, wp_ajax_ninja_forms_sendwp_remote_install_handler, did not have a capability check on it, nor did it have any nonce protection, therefore making it possible for low-level users, such as subscribers, to install and activate the SendWP Ninja Forms Contact Form – The Drag and Drop Form Builder for WordPress WordPress plugin before 3.4.34 and retrieve the client_secret key needed to establish the SendWP connection while also installing the SendWP plugin.
7.2CVE-2021-24889ninjaformsninja_forms+2
EPSS score
1.32%
The Ninja Forms Contact Form WordPress plugin before 3.6.4 does not escape keys of the fields POST parameter, which could allow high privilege users to perform SQL injections attacks
6.1CVE-2021-24165ninjaformsninja_forms+2
EPSS score
1.64%
In the Ninja Forms Contact Form WordPress plugin before 3.4.34, the wp_ajax_nf_oauth_connect AJAX action was vulnerable to open redirect due to the use of a user supplied redirect parameter and no protection in place.
4.3CVE-2021-24164ninjaformsninja_forms+2
EPSS score
0.89%
In the Ninja Forms Contact Form WordPress plugin before 3.4.34.1, low-level users, such as subscribers, were able to trigger the action, wp_ajax_nf_oauth, and retrieve the connection url needed to establish a connection. They could also retrieve the client_id for an already established OAuth connection.
6.5CVE-2021-34647ninjaformsninja_forms+2
EPSS score
1.16%
The Ninja Forms WordPress plugin is vulnerable to sensitive information disclosure via the bulk_export_submissions function found in the ~/includes/Routes/Submissions.php file, in versions up to and including 3.5.7. This allows authenticated attackers to export all Ninja Forms submissions data via the /ninja-forms-submissions/export REST API which can include personally identifiable information.
6.4CVE-2021-34648ninjaformsninja_forms+2
EPSS score
0.66%
The Ninja Forms WordPress plugin is vulnerable to arbitrary email sending via the trigger_email_action function found in the ~/includes/Routes/Submissions.php file, in versions up to and including 3.5.7. This allows authenticated attackers to send arbitrary emails from the affected server via the /ninja-forms-submissions/email-action REST API which can be used to socially engineer victims.
7.2CVE-2015-2220ninjaformsninja_forms+1
EPSS score
2.04%
Multiple cross-site scripting (XSS) vulnerabilities in the Ninja Forms plugin before 2.8.9 for WordPress allow (1) remote attackers to inject arbitrary web script or HTML via the ninja_forms_field_1 parameter in a ninja_forms_ajax_submit action to wp-admin/admin-ajax.php or (2) remote administrators to inject arbitrary web script or HTML via the fields[1] parameter to wp-admin/post.php.
9.8CVE-2016-1209ninjaformsninja_forms+1
EPSS score
61.61%
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via crafted serialized values in a POST request.
4.8CVE-2025-2561ninjaformsninja_forms+2
EPSS score
0.26%
The Ninja Forms WordPress plugin before 3.10.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
4.8CVE-2025-2524ninjaformsninja_forms+2
EPSS score
0.31%
The Ninja Forms WordPress plugin before 3.10.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).