CVE-2026-6248: wpForo Forum <= 3.0.5 - Authenticated (Subscriber+) Arbitrary File Deletion via Custom Profile Field File Path

Published Apr 20, 2026
·
Updated

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

1 affected component
wpForo wpForo Forum<=3.0.5

Event History

Apr 20, 2026
CVE Published
via MITRE·06:31 PM
Data Sourced
via MITRE·06:31 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Aug 7, 58287
Event
via FIRST·03:53 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

How do I fix CVE-2026-6248?

To fix CVE-2026-6248, update the wpForo Forum plugin to version 3.0.6 or later.

3

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.

4

Can CVE-2026-6248 be exploited remotely?

No, CVE-2026-6248 requires authenticated access, meaning an attacker must have at least Subscriber privileges.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203