Quick answers
- Is CVE-2026-110004 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110004 being exploited in the wild.
- How severe is CVE-2026-110004?
- Medium severity, with a CVSS score of 6.5, published 7 November 2026.
- Which products and versions are affected?
- wpForo Forum up to and including 3.2.2.
- Is there a fix for CVE-2026-110004?
- Yes: fixed in <UNKNOWN>. Until then: Administrators should avoid creating custom wpForo secondary usergroups with a blank WordPress role and the 'mth' (Manage Themes) capability, as this configuration enables the privilege escalation attack. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110004 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-110004?
- Check whether you run wpForo Forum at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: <UNKNOWN>
Administrators should avoid creating custom wpForo secondary usergroups with a blank WordPress role and the 'mth' (Manage Themes) capability, as this configuration enables the privilege escalation attack.
Technical details
The wpForo plugin's theme_delete function fails to properly validate file paths, allowing arbitrary file deletion. The vulnerability is compounded by a privilege escalation flaw: an unguarded wpforo_secondary_groupids[] POST parameter allows attackers to self-register and claim a custom usergroup with theme-management ('mth') capability, even as a subscriber. This requires an administrator to have configured a custom secondary usergroup with a blank WordPress role and the mth capability; the attacker can then exploit the file deletion to compromise the site.
Affected products
- wpForo wpForo Forum up to and including 3.2.2
Timeline
- 2026-11-07: disclosed