# CVE-2026-110004: wpForo Forum <= 3.2.2 - Authenticated (Subscriber+) Arbitrary File Deletion via Path Traversal via 'theme' Parameter

Status: published. Published: 2026-11-07. Updated: 2026-11-07.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- tomdever / wpForo Forum: ≥ 0; ≤ 3.2.2 (affected, semver). Source: CNA: Wordfence

## Severity and prioritization

- CVSS 3.1: 6.5 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; source: CNA: Wordfence

- CVSS 3.1: 6.5 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; source: NVD: security@wordfence.com

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-22

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/268f05d4-5f93-4d89-aa7f-c8731599dbc7?source=cve (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/classes/Actions.php#L2409 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/classes/Actions.php#L2405 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/classes/Members.php#L1428 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/includes/functions.php#L1659 (CNA: Wordfence)

- https://wordpress.org/plugins/wpforo/#developers (CNA: Wordfence)

- https://plugins.trac.wordpress.org/changeset?reponame=&new=3778162%40wpforo%2Ftags%2F3.2.3&old=3717441%40wpforo%2Ftags%2F3.2.2 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/classes/Actions.php#L2405 (security@wordfence.com)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/classes/Actions.php#L2409 (security@wordfence.com)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/classes/Members.php#L1428 (security@wordfence.com)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.2.2/includes/functions.php#L1659 (security@wordfence.com)

- https://plugins.trac.wordpress.org/changeset?reponame=&new=3778162%40wpforo%2Ftags%2F3.2.3&old=3717441%40wpforo%2Ftags%2F3.2.2 (security@wordfence.com)

- https://wordpress.org/plugins/wpforo/#developers (security@wordfence.com)

- https://www.wordfence.com/threat-intel/vulnerabilities/id/268f05d4-5f93-4d89-aa7f-c8731599dbc7?source=cve (security@wordfence.com)

## Provenance

- CNA: Wordfence: https://www.cve.org/CVERecord?id=CVE-2026-110004; retrieved 2026-11-07; source updated 2026-11-07

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110004; retrieved 2026-11-07; source updated 2026-11-07

Revision: a284569e9798d6990b50230e61320f2a4593389909bc083d46ffec08cc680463

Canonical: https://y2.dev/cve/CVE-2026-110004

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.