CVE-2026-9676
Deferred Deferred - Pending Action

Authenticated Post Modification in F4 Post Tree WordPress Plugin

Vulnerability report for CVE-2026-9676, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-29

Last updated on: 2026-06-29

Assigner: WPScan

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-29
Last Modified
2026-06-29
Generated
2026-07-19
AI Q&A
2026-06-29
EPSS Evaluated
2026-07-18
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
f4_post_tree plugin to 2.0.5 (exc)
f4_post_tree 2.0.5 to 2.0.5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The F4 Post Tree WordPress plugin versions before 2.0.5 have a vulnerability where they do not perform proper capability checks or CSRF/nonce verification on one of their AJAX actions.

This flaw allows authenticated users with Subscriber-level access or higher to modify the parent and menu order of arbitrary posts, which normally should be restricted.

Detection Guidance

This vulnerability can be detected by monitoring for unauthorized AJAX requests that attempt to modify the parent or menu order of posts. Specifically, look for AJAX calls related to the f4 Post Tree plugin's actions from authenticated users with Subscriber-level access or higher.

One approach is to capture and analyze HTTP requests to the WordPress site, focusing on AJAX endpoints used by the f4 Post Tree plugin. You can use tools like curl or wget to simulate such requests or inspect logs for suspicious activity.

  • Use curl to test the AJAX action with a crafted request to see if unauthorized post modifications are possible.
  • Example command: curl -X POST -b 'wordpress_logged_in_cookie' -d 'action=plugin_ajax_action&post_id=TARGET_POST_ID&parent=NEW_PARENT_ID&menu_order=NEW_ORDER' https://yourwordpresssite.com/wp-admin/admin-ajax.php

Replace 'wordpress_logged_in_cookie' with a valid authentication cookie for a Subscriber-level user, and adjust parameters accordingly. Monitoring logs for such requests or unexpected changes in post hierarchy can also help detect exploitation attempts.

Impact Analysis

This vulnerability can allow users with low-level access (Subscriber or above) to change the structure and order of posts on a WordPress site.

Such unauthorized modifications could disrupt site content organization, potentially leading to confusion for site visitors or misuse of content hierarchy.

Compliance Impact

The vulnerability in the f4 Post Tree WordPress plugin allows authenticated users with Subscriber-level access or higher to modify the parent and menu order of arbitrary posts due to missing capability checks and CSRF/nonce verification. This represents a broken access control issue (OWASP A5: Broken Access Control).

While the provided information does not explicitly mention compliance with standards such as GDPR or HIPAA, broken access control vulnerabilities can potentially lead to unauthorized modification of content, which may impact data integrity and confidentiality requirements under these regulations.

Therefore, organizations using affected versions of the plugin might face compliance risks if the vulnerability is exploited to alter sensitive or regulated content, but no direct compliance impact is detailed in the provided resources.

Mitigation Strategies

The immediate mitigation step is to update the f4 Post Tree WordPress plugin to version 2.0.5 or later, where this vulnerability has been fixed.

Until the update can be applied, restrict access to the plugin's AJAX actions by limiting authenticated user capabilities or implementing additional security measures such as Web Application Firewall (WAF) rules to block unauthorized AJAX requests.

Additionally, monitor user activity for suspicious post parent or menu order changes, especially from users with Subscriber-level access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9676. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart