Radar sectionsDatabase
Check my site
WordPress plugin

wpForo Forum <= 3.0.2 — Authenticated (Subscriber+) Arbitrary File Deletion via 'data[body][fileurl]' Parameter

CVE-2026-5809Published · Updated

Action summary

Affected: ≤3.0.2Update to 3.0.3 or newer

All remediation steps
Severity
High7.1
CVSS
7.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:H Availability
High
Weakness
CWE-73 External Control of File Name or Path
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

wpForo Forum wpforo

  1. Affected≤ 3.0.2
  2. Patched in3.0.3

Update to 3.0.3 or newer.

You are affected if you run ≤ 3.0.2. Version 3.0.3 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under wpForo Forum.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 3.0.3, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch wpForo Forum to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Leonid Semenenko (lsemenenko).

The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.2. This is due to a two-step logic flaw: the topic_add() and topic_edit() action handlers accept arbitrary user-supplied data[*] arrays from $_REQUEST and store them as postmeta without restricting which fields may contain array values. Because 'body' is included in the allowed topic fields list, an attacker can supply data[body][fileurl] with an arbitrary file path (e.g., wp-config.php or an absolute server path). This poisoned fileurl is persisted to the plugin's custom postmeta database table. Subsequently, when the attacker submits wpftcf_delete[]=body on a topic_edit request, the add_file() method retrieves the stored postmeta record, extracts the attacker-controlled fileurl, passes it through wpforo_fix_upload_dir() which only rewrites legitimate wpforo upload paths and returns all other paths unchanged, and then calls wp_delete_file() on the unvalidated path. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files writable by the PHP process on the server, including critical files such as wp-config.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in wpForo Forum

All 59
More vulnerabilities in wpForo Forum
SeverityVulnerabilityCVEPublished
High7.5Authenticated (Subscriber+) Privilege Escalation to 'data[secondary_groupids]' CSV Parameter
≤3.2.2Update to 3.2.3
CVE-2026-119164
High7.5Unauthenticated SQL Injection via 'data' Parameter
≤3.2.1Update to 3.2.2
CVE-2026-95870
Medium6.4Authenticated (Subscriber+) Stored Cross-Site Scripting via Reply Body in Moderation Forms
≤3.2.2Update to 3.2.3
CVE-2026-120532
High7.5Unauthenticated SQL Injection via 'href[locale]' Parameter
≤3.2.2Update to 3.2.3
CVE-2026-119155
Medium6.5Authenticated (Subscriber+) Arbitrary File Deletion via Path Traversal via 'theme' Parameter
≤3.2.2Update to 3.2.3
CVE-2026-110004

Timeline

  1. CVE published

    Severity high, CVSS 7.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?