Skip to content

CVE-2026-67187: Ninja Forms (< 3.15.4) Server-Side Validation Bypass via List Fields

Density:
C-Level Executive Briefing CVE-2026-67187 HIGH SCORE 84/100

A high-severity input validation vulnerability (CVE-2026-67187) was disclosed in the Ninja Forms WordPress plugin, impacting all versions prior to 3.15.4. With over 800,000 active installations worldwide, the vulnerability permits remote unauthenticated users to tamper with form submissions. During submission handling, list fields (such as radio buttons, select dropdowns, and checkboxes) failed to validate client-supplied values against the configured server-side option white list. Attackers can submit arbitrary string or numeric values to manipulate payment calculations, bypass business logic and mandatory conditional branching, or corrupt downstream CRM synchronizations.

HYBRID

HERMES THREAT SCORE & FORM INTEGRITY ASSESSMENT

Target: WordPress Ninja Forms Form Submission Engine (List Fields)
Confidence: 96%
84 / 100
HIGH

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 18 / 20
Threat Activity 14 / 20
Weaponization 16 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 15 / 20
Exploit Maturity 16 / 20
Attack Chain Potential 16 / 20
โš–๏ธ Divergence & Operational Rationale

CVSS v3.1 rates this at 7.5 (High) due to the complete loss of form data integrity without confidentiality compromise. Hermes scores this at 84 (High), accounting for widespread enterprise adoption of Ninja Forms for quote generation, custom checkout forms, and customer onboarding where parameter tampering directly translates to commercial fraud.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-67187: Ninja Forms (< 3.15.4) Server-Side Validation Bypass via List FieldsVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTMicrosoft Office & 365 Apps
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Microsoft Office & 365 Apps documented in Hermes dossier.”

Supporting Verified Evidence:

Ninja Forms relies on an asynchronous client-side JavaScript architecture to render dynamic form fields and manage conditional logic before dispatching the payload to the WordPress REST API or admin-ajax.php endpoint.

In versions prior to 3.15.4, the backend processing pipeline in includes/Fields/List.php inspected the submitted form fields as follows:

// Vulnerable implementation in Ninja Forms < 3.15.4
public function validate( $field, $data ) {
$field_value = $field['value'];
// Missing strict validation against configured list options!
if( empty( $field_value ) && $field['required'] ) {
return __( 'Field is required', 'ninja-forms' );
}
// Value accepted without verifying membership in $field['options']
return true;
}

Because the server only checked whether a required field was populatedโ€”without cross-referencing $field_value against the array of valid keys configured in $field['options']โ€”an attacker intercepting the HTTP request could substitute any arbitrary value.

  1. E-Commerce & Price Manipulation: On forms where list fields dictate item tiers, service levels, or donation amounts, adversaries can forge arbitrary zero or negative monetary values.
  2. Conditional Logic Bypass: Server-side actions dependent on specific dropdown selections can be triggered or bypassed regardless of front-end restrictions.
  3. Downstream Integration Poisoning: Corrupted field values propagate directly into integrated CRM systems (such as HubSpot, Salesforce, or Click5 CRM), causing database schema errors or dirty data injection.

An attacker submits an HTTP POST to the Ninja Forms AJAX handler with an arbitrary injected list option:

POST /wp-admin/admin-ajax.php HTTP/1.1
Host: target-site.com
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
action=nf_ajax_submit&formData=%7B%22id%22%3A1%2C%22fields%22%3A%7B%2214%22%3A%7B%22value%22%3A%22TAMPERED_CUSTOM_OVERRIDE_VAL%22%7D%7D%7D

In versions < 3.15.4, the server accepts TAMPERED_CUSTOM_OVERRIDE_VAL as valid input and commits it to the database submissions table and email notifications.


  1. Upgrade Ninja Forms Plugin: Update immediately to Ninja Forms 3.15.4 or later through the WordPress administrative dashboard (wp-admin/plugins.php) or WP-CLI:
    Terminal window
    wp plugin update ninja-forms --version=3.15.4
  2. Review Form Submissions: Audit recent form submissions containing calculated fields or payment elements for unexpected or out-of-bounds option values.
  3. Deploy Web Application Firewall (WAF) Rules: Apply inspection rules on nf_ajax_submit payloads to block unauthorized form parameters until updates are applied across multi-site networks.