CVE-2026-110004 · Package
NO FIX YET
The wpForo Forum WordPress plugin up to and including 3.2.2 fails to validate file paths in its theme_delete function. An authenticated subscriber can delete arbitrary files on the server, such as wp-config.php, which can lead to remote code execution.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running wpForo up to and including 3.2.2 are exposed to the file deletion. The chain described in the sources needs an administrator to have created a custom wpForo secondary usergroup with a blank WordPress role and the 'mth' capability; on sites without that configuration the attacker cannot claim theme-management access. Sites that do not run wpForo can skip it.
Not affected if default-config, no-custom-secondary-usergroup, plugin-not-installed
Who cares self-hosted, wordpress, wpforo
3.2.2 are affected.mth (Manage Themes) capability.No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.