dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-6248

HIGH · 8.1 CVSS v3.1 Published 2026-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The wpForo Forum plugin for WordPress contains an arbitrary file deletion vulnerability caused by two compounding flaws: the Members::update() method does not validate file-type custom profile field inputs, allowing authenticated users to store arbitrary paths; and the wpforo_fix_upload_dir() sanitization in ucf_file_delete() only remaps paths matching the expected pattern, passing arbitrary paths directly to unlink(). This allows subscriber-level attackers to delete any file accessible to the web server user, including wp-config.php for RCE.

MitigationUpgrade wpForo Forum plugin to version 3.0.6 or later. As a compensating control, disable the User Custom Fields addon plugin and review file permissions to prevent the web server user from deleting critical files like wp-config.php.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check wpForo Forum plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > wpForo Forum, or inspect the plugin header in wp-content/plugins/wpforoincludes/functions.php to find the 'Version' field
    Affected if version is 3.0.5 or lower (no version beyond 3.0.5 is specified)
  2. Verify User Custom Fields addon status
    In WordPress admin, go to wpForo > Addons or check if the User Custom Fields addon plugin is active in the Plugins list
    Affected if User Custom Fields addon is active and wpForo version is 3.0.5 or lower
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users and review roles; or query wp_usermeta table for users with wp_capabilities containing 'subscriber'
    Affected if any subscriber-level users exist in the WordPress installation
  4. Inspect ucf_file_delete function behavior
    Examine the wpforo_fix_upload_dir() function in the plugin files under wp-content/plugins/wpforoincludes/ - verify it only strips upload directory prefixes and passes result directly to unlink() without additional validation
    Affected if the function uses limited pattern matching and passes unsanitized paths to unlink()

User is affected if wpForo Forum plugin version is 3.0.5 or lower AND the User Custom Fields addon is enabled AND at least one subscriber-level user account exists in WordPress.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade wpForo Forum plugin to version 3.0.6 or later. As a compensating control, disable the User Custom Fields addon plugin and review file permissions to prevent the web server user from deleting critical files like wp-config.php.

Recommended fix Moderate confidence

wpForo Forum plugin version 3.0.6 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the wpForo Forum plugin
  4. If update available, click 'Update Now' to install the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/wpforo/ and upload via Plugins > Add New > Upload Plugin
  6. After update, verify the version is 3.0.6 or higher in Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6248 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6248 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data