# CVE-2026-87835: Front End Users <= 3.2.35 - Unauthenticated Membership Level and Account Status Self-Assignment


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-jmq3-353m-7wg2

## What is CVE-2026-87835?

CVE-2026-87835 is a medium-severity vulnerability in Unknown Front End Users, published on 24 Oct 2026. 

### Official description

The Front End Users WordPress plugin through 3.2.35 does not restrict which account attributes a visitor may set when registering through its front-end forms, allowing unauthenticated users to assign themselves an arbitrary membership level and to mark their own account as approved, confirmed and paid, bypassing the Front End Users WordPress plugin through 3.2.35's content restrictions and its registration gating.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-87835 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87835 is a medium-severity vulnerability in Unknown Front End Users, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-87835 in the wild and no public exploit code.

Affected product: Unknown Front End Users. 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-87835/ (Markdown: https://insights.sbomify.com/CVE-2026-87835/index.md)
```

## Sources

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

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