f4 Post Tree <= 2.0.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Parent/Menu Order Modification
Strategic Overview
- Status
- Patched in 2.0.5
- Affected Plugin
- F4 Post Tree
- Affected Version
<= 2.0.4- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-9676
At a glance
CVE-2026-9676 is a medium-severity Missing Authorization vulnerability in the F4 Post Tree WordPress plugin, affecting versions <= 2.0.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.5; sites on affected versions should update now. Disclosed August 2026, reported by Mustafa Ahmed.
Vulnerability Overview
The f4 Post Tree plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 2.0.4. This is due to a missing capability check and nonce verification on the ajax_move_tree_post() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify the parent post or menu order of arbitrary posts.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
F4 Post Tree <= 2.0.4 carries this weakness at ajax_move_tree_post(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For F4 Post Tree the fix is 2.0.5: builds <= 2.0.4 are affected, anything from 2.0.5 onward is not.
Remediation
Update to version 2.0.5, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: F4 Post Tree 2.0.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C