# CVE-2026-67187: Ninja Forms WordPress Plugin < 3.15.4 Server-Side Validation Bypass via List Fields


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-f833-cw2q-6hm3

## What is CVE-2026-67187?

CVE-2026-67187 is a medium-severity vulnerability in Saturday Drive Ninja Forms, published on 28 Oct 2026. 

### Official description

Ninja Forms plugin for WordPress before 3.15.4 contains an incomplete server-side validation vulnerability that allows unauthenticated attackers to submit arbitrary values to Checkbox List, Multi-Select List, Image List, Country, and State fields because NF_Abstracts_List falls through to a validate() method that only checks required-field presence. Attackers can submit crafted formula payloads through the unauthenticated nf_ajax_submit endpoint that bypass CSV escaping applied only to Textbox and Textarea fields, resulting in CSV injection when an administrator downloads and opens the exported submissions file.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

## Which versions are affected by CVE-2026-67187?


## How do I fix CVE-2026-67187?

No fix has been published for CVE-2026-67187 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67187 being exploited?

There is no known exploitation of CVE-2026-67187 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67187 and fix it if it is affected.

What it is: CVE-2026-67187 is a medium-severity vulnerability in Saturday Drive Ninja Forms, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-67187 in the wild and no public exploit code.

Affected product: Saturday Drive Ninja Forms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67187/ (Markdown: https://insights.sbomify.com/CVE-2026-67187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67187
- OSV: https://osv.dev/vulnerability/CVE-2026-67187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67187/
Summaries are generated and may contain mistakes; the official description above is the record.