# CVE-2025-15691: WPFunnels < 3.13.0 - Unauthenticated User Registration via Opt-in Forms

> Unauthenticated attackers can create WordPress user accounts via opt-in forms even when site registration is disabled, bypassing intended access controls.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-23pq-j2qq-jh57

## What is CVE-2025-15691?

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

### Official description

The WPFunnels  WordPress plugin before 3.13.0 does not check whether user registration is enabled on the site before creating accounts from opt-in form submissions, relying on a value supplied in the request instead, allowing unauthenticated attackers to create WordPress user accounts even when registration is disabled.

This is an incomplete fix for CVE-2025-12353: the check added in 3.6.3 covers only one of the three registration paths.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-15691?


## How do I fix CVE-2025-15691?

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

## Is CVE-2025-15691 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15691 and fix it if it is affected.

What it is: CVE-2025-15691 is a medium-severity missing authorization vulnerability in Unknown WPFunnels, published on 4 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-2025-15691 in the wild and no public exploit code.

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

## Sources

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

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