wpForo Forum <= 3.2.2 - Authenticated (Subscriber+) Arbitrary File Deletion via Path Traversal via 'theme' Parameter
Strategic Overview
- Status
- Patched in 3.2.3
- Affected Plugin
- wpForo Forum
- Affected Version
<= 3.2.2- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory
- CVE
CVE-2026-110004
At a glance
CVE-2026-110004 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory vulnerability in the wpForo Forum WordPress plugin, affecting versions <= 3.2.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed November 2026, reported by jiahao.
Vulnerability Overview
The wpForo Forum plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the theme_delete function in all versions up to, and including, 3.2.2 This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). This exploit chain is reachable only on sites where an administrator has created a custom wpForo secondary usergroup with a blank WordPress role and the 'mth' (Manage Themes) capability; on such sites, an attacker can self-register and claim that group via the unguarded wpforo_secondary_groupids[] POST field, bypassing the role-based group filter and gaining theme-management access as a Subscriber.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory
wpForo Forum <= 3.2.2 carries this weakness at mth, and reaching it takes an account at Subscriber level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For wpForo Forum the fix is 3.2.3: builds <= 3.2.2 are affected, anything from 3.2.3 onward is not.
Remediation
Update to version 3.2.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: wpForo Forum 3.2.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in wpForo Forum
- 9.9CVE-2024-3200: wpForo Forum <= 2.3.3 SQL Injection
CVE-2024-3200 - 9.8CVE-2023-47868: wpForo Forum <= 2.2.3 Privilege Escalation
CVE-2023-47868 - 9.8CVE-2018-16613: wpForo < = 1.5.1 Privilege Escalation
CVE-2018-16613 - 9.8CVE-2018-11515: wpForo Forum <= 1.4.12 SQL Injection
CVE-2018-11515 - 8.8CVE-2026-0910: wpForo Forum <= 2.4.13 PHP Object Injection
CVE-2026-0910 - 8.8CVE-2025-31420: wpForo Forum <= 2.4.3 Privilege Escalation
CVE-2025-31420 - 8.8CVE-2023-2249: wpForo Forum Local File Include, SSRF, and PHAR
CVE-2023-2249 - 8.8CVE-2022-40200: wpForo Forum <= 2.0.9 Arbitrary File Upload
CVE-2022-40200
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C