CVE-2026-6248: wpForo Forum <= 3.0.5 - Authenticated (Subscriber+) Arbitrary File Deletion via Custom Profile Field File Path
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 wpforofixuploaddir() sanitization function in ucffiledelete() 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6248?
CVE-2026-6248 has a high severity due to its potential for arbitrary file deletion by authenticated users.
How do I fix CVE-2026-6248?
To fix CVE-2026-6248, update the wpForo Forum plugin to version 3.0.6 or later.
Who is affected by CVE-2026-6248?
CVE-2026-6248 affects users of the wpForo Forum plugin for WordPress, specifically versions up to and including 3.0.5.
Can CVE-2026-6248 be exploited remotely?
No, CVE-2026-6248 requires authenticated access, meaning an attacker must have at least Subscriber privileges.
What are the implications of CVE-2026-6248?
The implications of CVE-2026-6248 include the risk of unauthorized file deletion, which can lead to data loss or further exploitation.