# CVE-2026-4666: Missing authorization in wpForo Forum

> Authenticated subscribers can arbitrarily modify any forum post, including private and admin posts, due to missing authorization checks in the wpForo Forum plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-gq2v-mwv7-cvm2

## What is CVE-2026-4666?

CVE-2026-4666 is a medium-severity missing authorization vulnerability in tomdever wpForo Forum, published on 17 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The wpForo Forum plugin for WordPress is vulnerable to unauthorized modification of data due to the use of `extract($args, EXTR_OVERWRITE)` on user-controlled input in the `edit()` method of `classes/Posts.php` in all versions up to, and including, 2.4.16. The `post_edit` action handler in `Actions.php` passes `$_REQUEST['post']` directly to `Posts::edit()`, which calls `extract($args, EXTR_OVERWRITE)`. An attacker can inject `post[guestposting]=1` to overwrite the local `$guestposting` variable, causing the entire permission check block to be skipped. The nonce check uses a hardcoded `wpforo_verify_form` action shared across all 8 forum templates, so any user who can view any forum page obtains a valid nonce. This makes it possible for authenticated attackers, with Subscriber-level access and above, to edit the title, body, name, and email fields of any forum post, including posts in private forums, admin posts, and moderator posts. Content passes through `wpforo_kses()` which strips JavaScript but allows rich HTML.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-4666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4666 is a medium-severity missing authorization vulnerability in tomdever wpForo Forum, published on 17 Apr 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-4666 in the wild and no public exploit code.

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

## Sources

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

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