# CVE-2026-19220: Forminator Forms < 1.57.1 - Unauthenticated Multisite Site Creation and Privilege Escalation

> Unauthenticated attackers can create new sites on WordPress multisite networks and gain administrator privileges if site registration is enabled.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-wjxr-7w8m-64j5

## What is CVE-2026-19220?

CVE-2026-19220 is a low-severity vulnerability in Unknown Forminator Forms, published on 26 Aug 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.1 does not verify that site registration is enabled on the network before creating a site signup, allowing unauthenticated visitors to create a new site on a WordPress multisite network and gain administrator privileges on it.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-19220 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19220 is a low-severity vulnerability in Unknown Forminator Forms, published on 26 Aug 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-19220 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-19220/ (Markdown: https://insights.sbomify.com/CVE-2026-19220/index.md)
```

## Sources

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

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