# CVE-2026-79618: WP User Frontend < 4.3.12 - Subscriber+ Post Creation via Subscription-Gated Form


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-5f7g-qp7c-jr44

## What is CVE-2026-79618?

CVE-2026-79618 is a medium-severity vulnerability in Unknown WP User Frontend, published on 2 Oct 2026. 

### Official description

The WP User Frontend WordPress plugin before 4.3.12 does not enforce its subscription-purchase requirement in one of its post-creation handlers, allowing authenticated users with subscriber-level access and above to create and, depending on the form's configuration, immediately publish posts through forms restricted to paying subscribers.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-79618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79618 is a medium-severity vulnerability in Unknown WP User Frontend, published on 2 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-79618 in the wild and no public exploit code.

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

## Sources

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

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