# CVE-2026-87071: Forminator Forms < 1.57.2.1 - Unauthenticated Post Meta Injection on Submitted Posts

> Unauthenticated attackers can inject arbitrary metadata into posts created via public forms in the Forminator Forms plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-p6xg-237f-rf4g

## What is CVE-2026-87071?

CVE-2026-87071 is a medium-severity missing authorization vulnerability in Unknown Forminator Forms, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Forminator Forms WordPress plugin before 1.57.2.1 does not restrict which metadata keys a form submission may supply, and does not exclude the keys WordPress reserves for its own use, so unauthenticated visitors submitting a public form that collects post content can attach metadata of their choosing to the post their submission creates.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-87071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87071 is a medium-severity missing authorization vulnerability in Unknown Forminator Forms, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87071 in the wild and no public exploit code.

Affected product: Unknown Forminator 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-87071/ (Markdown: https://insights.sbomify.com/CVE-2026-87071/index.md)
```

## Sources

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

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