# CVE-2026-9676: f4 Post Tree < 2.0.5 - Subscriber+ Arbitrary Post Parent/Menu Order Modification

> Authenticated subscribers can modify arbitrary post parents and menu orders due to missing capability checks in the F4 Post Tree plugin.

- **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:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-m9qg-5xmj-j7gg

## What is CVE-2026-9676?

CVE-2026-9676 is a medium-severity missing authorization vulnerability in Unknown F4 Post Tree, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The F4 Post Tree WordPress plugin before 2.0.5 does not perform capability checks or CSRF/nonce verification on one of its AJAX actions, allowing authenticated users with Subscriber-level access and above to modify the parent and menu order of arbitrary posts.

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


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

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

## Is CVE-2026-9676 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9676 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9676 is a medium-severity missing authorization vulnerability in Unknown F4 Post Tree, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9676 exists.

Affected product: Unknown F4 Post Tree. 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-9676/ (Markdown: https://insights.sbomify.com/CVE-2026-9676/index.md)
```

## Sources

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

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