CVE-2026-67187: Ninja Forms (< 3.15.4) Server-Side Validation Bypass via List Fields
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.
HERMES THREAT SCORE & FORM INTEGRITY ASSESSMENT
Target:WordPress Ninja Forms Form Submission Engine (List Fields) 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.
CVE-2026-67187: Ninja Forms (< 3.15.4) Server-Side Validation Bypass via List FieldsVULNERABILITY
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.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Flaw Analysis
Section titled โ1. Technical Flaw Analysisโ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.4public 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.
Operational Consequences:
Section titled โOperational Consequences:โ- 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.
- Conditional Logic Bypass: Server-side actions dependent on specific dropdown selections can be triggered or bypassed regardless of front-end restrictions.
- 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.
2. Exploitation Proof of Concept
Section titled โ2. Exploitation Proof of Conceptโ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.1Host: target-site.comContent-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%7DIn 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.
3. Remediation & Hardening
Section titled โ3. Remediation & Hardeningโ- 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 - Review Form Submissions: Audit recent form submissions containing calculated fields or payment elements for unexpected or out-of-bounds option values.
- Deploy Web Application Firewall (WAF) Rules:
Apply inspection rules on
nf_ajax_submitpayloads to block unauthorized form parameters until updates are applied across multi-site networks.