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.
Problem types
CWE-73 External Control of File Name or Path
Product status
Any version
Timeline
| 2026-04-08: | Vendor Notified |
| 2026-04-10: | Disclosed |
Credits
Leonid Semenenko
References
www.wordfence.com/…-89ee-4480-bb96-83f2044a4323?source=cve
plugins.trac.wordpress.org/changeset/3503313/wpforo
plugins.trac.wordpress.org/…tags/3.0.2/classes/Actions.php
plugins.trac.wordpress.org/…tags/3.0.2/classes/Actions.php
plugins.trac.wordpress.org/…o/tags/3.0.2/classes/Posts.php
plugins.trac.wordpress.org/…ags/3.0.2/classes/PostMeta.php
plugins.trac.wordpress.org/…ags/3.0.2/classes/PostMeta.php
plugins.trac.wordpress.org/…ags/3.0.2/classes/PostMeta.php
plugins.trac.wordpress.org/…s/3.0.2/includes/functions.php
