dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-6262

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Betheme theme for WordPress is vulnerable to Arbitrary File Deletion in versions up to, and including, 28.4. This is due to the upload_icons() function workflow using a user-controlled upload path (`mfn-icon-upload`) in a filesystem move operation without constraining it to the uploads directory. This makes it possible for authenticated attackers, with contributor-level access and above, to move/delete arbitrary local files via path traversal.

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 Betheme WordPress theme versions up to 28.4 contain a path traversal vulnerability in the upload_icons() function. Authenticated users with contributor-level access can manipulate the mfn-icon-upload parameter to perform arbitrary file deletions via filesystem move operations outside the intended uploads directory.

MitigationUpdate the Betheme theme to version 28.5 or later where the vulnerability is patched. Until then, limit contributor-level access and monitor for suspicious file deletion attempts.

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
None

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

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. Identify Betheme theme version
    In WordPress admin, go to Appearance > Themes and locate Betheme to view its version number, or check the style.css file in wp-content/themes/betheme/ for the 'Version:' header
    Affected if The version is 28.4 or earlier (any version up to and including 28.4)
  2. Locate the upload_icons function
    Search the theme files for the function upload_icons() - typically found in functions.php or included template files within the betheme directory
    Affected if The function exists and contains logic that processes the mfn-icon-upload parameter without proper path sanitization
  3. Verify contributor-level user accounts
    In WordPress admin, go to Users and review roles. Contributor role allows authenticated access to theme features.
    Affected if Any user with contributor role or higher exists in the WordPress installation
  4. Check access to vulnerable parameter
    Review theme AJAX handlers or form submissions that accept the mfn-icon-upload parameter, typically in admin-ajax.php or theme-specific AJAX endpoints
    Affected if The parameter is accepted and processed by the upload_icons function without validating the destination path remains within the uploads directory
  5. Monitor for suspicious file deletion activity
    Review server access logs and WordPress audit logs for unusual delete or move operations, particularly requests to admin-ajax.php with mfn-icon-upload or similar icon upload actions
    Affected if Evidence exists of file deletion operations targeting paths outside wp-content/uploads/

You are affected if the Betheme theme version is 28.4 or earlier AND contributor-level users can access the upload_icons function via the mfn-icon-upload parameter without path validation.

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

Update the Betheme theme to version 28.5 or later where the vulnerability is patched. Until then, limit contributor-level access and monitor for suspicious file deletion attempts.

Recommended fix Moderate confidence

Latest version above 28.4 (check support.muffingroup.com for exact release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Betheme theme
  4. 4. Check the current version number displayed
  5. 5. If the version is 28.4 or below, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest Betheme theme from the official source (support.muffingroup.com) and upload it via Appearance > Themes > Add New > Upload Theme
  7. 7. After updating, verify the new version number in the themes section

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6262 — 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-6262 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