# CVE-2026-79631: WPFunnels < 3.13.0 - Unauthenticated Order and Opt-In PII Disclosure via Web-Accessible Log Files

> Unauthenticated attackers can download sensitive customer order and opt-in data from publicly accessible log files in the WPFunnels WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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-cv99-jq97-cc3r

## What is CVE-2026-79631?

CVE-2026-79631 is a medium-severity 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 restrict access to the log files it writes to a predictable location under the public uploads directory, allowing unauthenticated users to download customer order details and opt-in form submissions when logging is enabled.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-79631 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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