# CVE-2026-79632: WPFunnels < 3.13.0 - Unauthenticated Arbitrary Recipient Email Sending via wpfnl_shortcode_optin_submission

> Unauthenticated attackers can send arbitrary emails to any recipient via the opt-in submission handler due to missing authorization checks.

- **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-4w2x-h688-7527

## What is CVE-2026-79632?

CVE-2026-79632 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 perform any authorisation or nonce check in one of its opt-in submission handlers, and takes the notification recipients and subject from the request, allowing unauthenticated users to make the site send emails to arbitrary recipients with an arbitrary subject.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-79632 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79632 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-2026-79632 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-2026-79632/ (Markdown: https://insights.sbomify.com/CVE-2026-79632/index.md)
```

## Sources

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

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