MEDIUM 6.5

CVE-2026-8380: Frontend File Manager Plugin Arbitrary Post Deletion Vulnerability

The Frontend File Manager Plugin for WordPress versions through 23.6 contains a flaw that allows authorized users to delete posts and pages they do not own. Specifically, any user with author-level permissions or higher can permanently remove arbitrary content from a WordPress site. If an administrator enables the plugin's "Allow guest uploads" setting, this same destructive capability becomes available to unauthenticated visitors, significantly expanding the attack surface.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Weaknesses (CWE)
Affected products
0 configuration(s)
Published / Modified
2026-06-26 / 2026-06-26

NVD description (verbatim)

The Frontend File Manager Plugin WordPress plugin through 23.6 does not properly verify ownership of every targeted post before permanent deletion, allowing authenticated users with author-level access and above to permanently delete arbitrary posts and pages. When the Frontend File Manager Plugin WordPress plugin through 23.6's "Allow guest uploads" setting is enabled by an administrator, the same deletion primitive becomes reachable by unauthenticated users.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-8380 stems from insufficient authorization checks in the Frontend File Manager Plugin's post deletion functionality. The plugin fails to verify post ownership before executing permanent deletion operations. The vulnerability chain involves two distinct attack vectors: (1) Authenticated exploitation by users with author or higher privileges, and (2) Unauthenticated exploitation when guest upload functionality is enabled, as this setting inadvertently allows guest users to reach the deletion primitive. The root cause is a missing or inadequate authorization gate that should restrict deletion actions to post authors or administrators.

Business impact

Content deletion attacks damage site integrity and disrupt business continuity. An attacker with author access could selectively erase critical pages, product information, or published content to sabotage operations or damage reputation. If guest uploads are enabled, the risk escalates dramatically—any unauthenticated visitor can wipe the entire site's published content. For WordPress sites operating as content platforms, e-commerce stores, or information repositories, this vulnerability threatens data availability and could force operational downtime for recovery and restoration efforts.

Affected systems

The Frontend File Manager Plugin through version 23.6 is affected. All WordPress installations running this plugin version or earlier are at risk if any user account with author-level access exists. Sites that have enabled the "Allow guest uploads" setting face maximum risk, as the vulnerability becomes remotely exploitable without authentication.

Exploitability

The vulnerability is straightforward to exploit. Authenticated attackers with author permissions can invoke the deletion function directly through the plugin interface or API. The attack requires no user interaction, no complex setup, and no code execution—only HTTP requests targeting the deletion endpoint with a valid post ID. When guest uploads are enabled, an unauthenticated attacker can perform the same action, making the vulnerability trivially accessible. The CVSS score of 6.5 (MEDIUM) reflects the combination of high impact (integrity and availability) offset by the requirement of high privilege level in the authenticated scenario.

Remediation

Update the Frontend File Manager Plugin to a patched version that implements proper post ownership verification before deletion. Verify against the vendor advisory for the specific fixed version number. As an interim mitigation, disable the "Allow guest uploads" setting immediately if enabled, which eliminates the unauthenticated attack vector. Review user roles and remove author-level access from accounts that do not require it. Additionally, implement WordPress backup and version control practices to enable rapid content restoration if exploitation occurs.

Patch guidance

Check the WordPress plugin repository or the vendor's security advisory for a version number that addresses this authorization flaw. Apply updates through the WordPress admin dashboard or manually via SFTP. After updating, verify that the "Allow guest uploads" setting remains disabled unless explicitly required. Test the plugin's deletion functionality with a non-privileged author account to confirm that arbitrary post deletion is no longer possible.

Detection guidance

Monitor WordPress logs and audit trails for deletion of posts by accounts that did not create them. Review user activity logs for post deletions by author-level accounts that target high-value content. If guest uploads are enabled, watch for any deletion activity originating from unauthenticated requests. Enable WordPress security plugins that log post modifications and deletions, and set alerts for bulk or anomalous content removal. Check the Frontend File Manager Plugin's activity logs if available.

Why prioritize this

This vulnerability merits rapid attention due to its direct impact on content availability and integrity. While the authenticated attack vector requires prior account compromise or insider threat, the unauthenticated vector (when guest uploads are enabled) is trivially accessible. Organizations using this plugin should prioritize patching immediately, particularly if guest uploads are active. The ability to permanently delete arbitrary content without recovery potential represents a high business risk despite the MEDIUM CVSS score.

Risk score, explained

The CVSS 3.1 score of 6.5 reflects a MEDIUM severity. The scoring factors are: Attack Vector (Network) and Attack Complexity (Low) indicate easy remote accessibility; Privileges Required (High) penalizes the authenticated scenario but acknowledges that high-privilege accounts are often available or compromisable; the lack of Confidentiality impact keeps the score moderate; Integrity and Availability impacts are both rated High because permanent content deletion directly harms both. The score does not fully capture the risk of the unauthenticated guest upload variant—organizations should treat the effective risk as higher if that setting is active.

Frequently asked questions

If we disable guest uploads, are we fully protected?

Disabling guest uploads eliminates the unauthenticated attack vector, but authenticated users with author-level access or above can still delete arbitrary posts until you patch. You must apply the vendor's security update to close both attack paths.

Can we use WordPress backups to recover deleted posts?

Yes, if you maintain regular backups and detect the attack promptly. However, relying on backups is a reactive measure. Patching the plugin prevents the deletion from occurring in the first place and is the primary defense.

Does this affect administrators or only author-level users?

The vulnerability affects any user with author-level privileges or higher. Administrators can always perform deletions as part of normal duties, so the flaw is most critical for author accounts, which should only delete their own content. Verify that your author-level accounts are operated by trusted staff.

What should we do if we suspect our site has been exploited?

Restore from your most recent clean backup, then patch the plugin. Review access logs and user activity to determine if unauthorized deletions occurred. Consider auditing user permissions and strengthening authentication (e.g., requiring stronger passwords or enabling multi-factor authentication).

This analysis is provided for informational purposes to assist security professionals in risk assessment and mitigation planning. The technical details, remediation guidance, and risk prioritization are based on the published vulnerability description and CVSS scoring. Organizations should verify patch availability and compatibility with their specific WordPress environment before deployment. This explainer does not constitute professional security advice, and security teams should consult with their vendors and conduct thorough testing in non-production environments prior to patching. SEC.co does not warrant the completeness or accuracy of third-party security information and recommends independent verification of all remediation steps. Source: NVD (public-domain), retrieved 2026-08-04. Analysis generated by SEC.co (claude-haiku-4-5).