# CVE-2026-12698: wpForo Forum < 3.1.3 - Subscriber+ Account Status and Reputation Manipulation via Profile Update Mass Assignment

> Subscribers can manipulate account status and reputation fields via mass assignment, potentially bypassing bans and forging scores.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-898j-cg5m-8wj7

## What is CVE-2026-12698?

CVE-2026-12698 is a medium-severity missing authorization vulnerability in Unknown wpForo Forum, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The wpForo Forum WordPress plugin before 3.1.3 does not restrict which profile fields a member may set when editing their own account, allowing users with a subscriber-level account to write administrator-controlled account-state and reputation fields on their own profile, including self-activating a pending or banned account and forging their forum reputation score.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-12698 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12698 is a medium-severity missing authorization vulnerability in Unknown wpForo Forum, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12698 in the wild and no public exploit code.

Affected product: Unknown wpForo Forum. 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-12698/ (Markdown: https://insights.sbomify.com/CVE-2026-12698/index.md)
```

## Sources

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

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