Description
The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.2. This is due to a two-step logic flaw: the topic_add() and topic_edit() action handlers accept arbitrary user-supplied data[*] arrays from $_REQUEST and store them as postmeta without restricting which fields may contain array values. Because 'body' is included in the allowed topic fields list, an attacker can supply data[body][fileurl] with an arbitrary file path (e.g., wp-config.php or an absolute server path). This poisoned fileurl is persisted to the plugin's custom postmeta database table. Subsequently, when the attacker submits wpftcf_delete[]=body on a topic_edit request, the add_file() method retrieves the stored postmeta record, extracts the attacker-controlled fileurl, passes it through wpforo_fix_upload_dir() which only rewrites legitimate wpforo upload paths and returns all other paths unchanged, and then calls wp_delete_file() on the unvalidated path. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files writable by the PHP process on the server, including critical files such as wp-config.
Published: 2026-04-11
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Arbitrary File Deletion
Action: Patch
AI Analysis

Impact

wpForo Forum for WordPress has a flaw that allows authenticated users with subscriber-level access to specify any file path in the data[body][fileurl] field during topic creation or editing. The plugin does not validate this value and stores it in postmeta. When an edit is submitted with wpftcf_delete[]=body, the plugin retrieves the stored path, uses wpforo_fix_upload_dir() which rewrites only valid upload paths and leaves other paths untouched, and then calls wp_delete_file() on it. This results in arbitrary file deletion, including critical files such as wp-config.php, and represents a CWE‑73 file path traversal weakness.

Affected Systems

The vulnerability affects installations of the wpForo Forum plugin by tomdever running version 3.0.2 or older. The flaw resides in the topic_add() and topic_edit() handlers and the add_file() method invoked during editing.

Risk and Exploitability

The CVSS score of 7.1 indicates high impact. Exploitation requires authentication; any user with subscriber-level privileges or higher can trigger the deletion. While no public exploit has been documented and EPSS is unavailable, the logic is simple and could be abused on any site where the PHP process can write to the target file path. The vulnerability is not yet listed in the CISA KEV catalog.

Generated by OpenCVE AI on April 11, 2026 at 09:50 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade wpForo Forum to the latest release (above 3.0.2).
  • Verify that the plugin settings restrict file deletion to administrators.
  • Restrict PHP process write permissions on critical directories such as wp-config.php and wp-content.

Generated by OpenCVE AI on April 11, 2026 at 09:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 13 Apr 2026 16:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 13 Apr 2026 13:00:00 +0000

Type Values Removed Values Added
First Time appeared Tomdever
Tomdever wpforo Forum
Wordpress
Wordpress wordpress
Vendors & Products Tomdever
Tomdever wpforo Forum
Wordpress
Wordpress wordpress

Sat, 11 Apr 2026 08:00:00 +0000

Type Values Removed Values Added
Description The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.2. This is due to a two-step logic flaw: the topic_add() and topic_edit() action handlers accept arbitrary user-supplied data[*] arrays from $_REQUEST and store them as postmeta without restricting which fields may contain array values. Because 'body' is included in the allowed topic fields list, an attacker can supply data[body][fileurl] with an arbitrary file path (e.g., wp-config.php or an absolute server path). This poisoned fileurl is persisted to the plugin's custom postmeta database table. Subsequently, when the attacker submits wpftcf_delete[]=body on a topic_edit request, the add_file() method retrieves the stored postmeta record, extracts the attacker-controlled fileurl, passes it through wpforo_fix_upload_dir() which only rewrites legitimate wpforo upload paths and returns all other paths unchanged, and then calls wp_delete_file() on the unvalidated path. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files writable by the PHP process on the server, including critical files such as wp-config.
Title wpForo Forum <= 3.0.2 - Authenticated (Subscriber+) Arbitrary File Deletion via 'data[body][fileurl]' Parameter
Weaknesses CWE-73
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H'}


Subscriptions

Tomdever Wpforo Forum
Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-04-13T15:15:07.646Z

Reserved: 2026-04-08T15:01:41.066Z

Link: CVE-2026-5809

cve-icon Vulnrichment

Updated: 2026-04-13T15:11:26.235Z

cve-icon NVD

Status : Deferred

Published: 2026-04-11T08:16:05.503

Modified: 2026-04-24T18:00:32.033

Link: CVE-2026-5809

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-13T12:56:36Z

Weaknesses