sales@hackhalt.com

Home / Threats / CVE-2026-110004

Wpforo - Security Vulnerability (CVE-2026-110004)

CVE-2026-110004

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.

CVE-2026-110004

MEDIUM CVSS 6.5 Published 2026-11-07 Updated 2026-11-08
AI Risk Elevated (64/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected Components 2
Reference Links 7
AI Risk Engine Elevated (64/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-11-07 CVE published and first recorded in the threat feed.
  2. 2026-11-08 Record updated with latest vulnerability metadata.
  3. 2026-11-08 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 3 days ago

AI enriched 3 days ago (2026-11-08 19:02 UTC)

Technical Summary

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…

Potential Impact

Severity is MEDIUM (CVSS 6.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 64/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Wpforo PLUGIN · wpforo Affected: <= 3.2.2 Fixed version not specified
wpForo Forum PLUGIN · wpforo-forum Affected: <= 3.2.2 Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Wpforo to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Wpforo, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Wpforo. An attacker needs any registered account, so open registration materially increases the risk.

How do I fix it?

Update Wpforo to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Remote Code Execution flaw. An attacker who exploits it can run their own code on the server, which is total control of the site.