CVE-2026-6248
published 2026-04-20CVE-2026-6248: The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.5. This is due to two compounding flaws: the…
PriorityP355high8.1CVSS 3.1
AVNACLPRLUINSUCNIHAH
EPSS
0.59%
43.9th percentile
The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.5. This is due to two compounding flaws: the Members::update() method does not validate or restrict the value of file-type custom profile fields, allowing authenticated users to store an arbitrary path instead of a legitimate upload path; and the wpforo_fix_upload_dir() sanitization function in ucf_file_delete() only remaps paths that match the expected pattern, and it is passed directly to the unlink() function. 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). Note: The vulnerability requires a file custom field, which requires the wpForo - User Custom Fields addon plugin.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| tomdever | wpforo_forum | <= 3.0.5 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-9xxq-3rc5-mg2v: The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3
ghsa_unreviewed·2026-04-20
CVE-2026-6248 [HIGH] CWE-22 GHSA-9xxq-3rc5-mg2v: The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3
The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.5. This is due to two compounding flaws: the Members::update() method does not validate or restrict the value of file-type custom profile fields, allowing authenticated users to store an arbitrary path instead of a legitimate upload path; and the wpforo_fix_upload_dir() sanitization function in ucf_file_delete() only remaps paths that match the expected pattern, and it is passed directly to the unlink() function. 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). Note: The vulnerability requires
VulDB
tomdever wpForo Forum Plugin up to 3.0.5 on WordPress Members::update path traversal (EUVD-2026-23935)
vuldb·2026-04-20·CVSS 8.1
CVE-2026-6248 [HIGH] tomdever wpForo Forum Plugin up to 3.0.5 on WordPress Members::update path traversal (EUVD-2026-23935)
A vulnerability was found in tomdever wpForo Forum Plugin up to 3.0.5 on WordPress. It has been classified as critical. This affects the function Members::update. The manipulation leads to path traversal.
This vulnerability is traded as CVE-2026-6248. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is recommended.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://plugins.trac.wordpress.org/browser/wpforo/tags/2.4.16/wpforo/classes/Actions.php#L1418https://plugins.trac.wordpress.org/browser/wpforo/tags/2.4.16/wpforo/classes/Members.php#L891https://plugins.trac.wordpress.org/browser/wpforo/tags/2.4.16/wpforo/includes/functions.php#L3187https://plugins.trac.wordpress.org/changeset/3509997/wpforohttps://www.wordfence.com/threat-intel/vulnerabilities/id/79cc102a-6777-41be-a395-8c2eeb6deb73?source=cve
2026-04-20
Published