dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-6423

HIGH · 8.8 CVSS v3.1 Published 2025-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 BeeTeam368 Extensions plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the handle_submit_upload_file() function in all versions up to, and including, 2.3.5. This makes it possible for authenticated attackers with Subscriber-level access or higher to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 BeeTeam368 Extensions WordPress plugin is vulnerable to arbitrary file uploads in the handle_submit_upload_file() function due to missing file type validation. This allows authenticated users with Subscriber-level access or higher to upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate BeeTeam368 Extensions to version 2.3.6 or later which includes proper file type validation. If immediate patching is not feasible, disable the plugin or restrict subscriber-level user registration.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm BeeTeam368 Extensions is installed
    Navigate to WordPress Admin > Plugins and look for 'BeeTeam368 Extensions' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder named 'bt368' or similar
    Affected if The plugin is not present in the installation, then the user is not affected by this specific vulnerability
  2. Identify the installed plugin version
    In WordPress Admin > Plugins, click on the BeeTeam368 Extensions plugin to view its details, or read the main plugin PHP file (usually plugin-name.php) to find the 'Version' header in the plugin comments
    Affected if The installed version is lower than 2.3.6 (e.g., 2.3.5, 2.3.0, 1.x.x), then the plugin is vulnerable
  3. Verify subscriber-level users exist
    In WordPress Admin > Users, review the list of users and check if any accounts have the 'Subscriber' role, or check if user registration is enabled at Settings > General > 'Membership' (Anyone can register)
    Affected if There are active subscriber-level accounts or subscriber registration is enabled, then the upload attack surface is exposed
  4. Check if upload functionality is accessible
    Inspect the WordPress site for any frontend forms that accept file uploads provided by the plugin (commonly triggered via AJAX to endpoint like wp-admin/admin-ajax.php with action 'submit_upload_file' or similar), or check the plugin source code for handle_submit_upload_file function availability
    Affected if The upload form or AJAX endpoint exists and is accessible to authenticated users, the arbitrary file upload vulnerability is exploitable

A user is affected if the BeeTeam368 Extensions plugin is installed with a version lower than 2.3.6 AND subscriber-level user accounts can access the plugin's upload functionality.

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 BeeTeam368 Extensions to version 2.3.6 or later which includes proper file type validation. If immediate patching is not feasible, disable the plugin or restrict subscriber-level user registration.

Recommended fix Moderate confidence

BeeTeam368 Extensions version 2.3.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the BeeTeam368 Extensions plugin
  4. 4. Check the current installed version (should be 2.3.5 or below)
  5. 5. Navigate to Plugins > Add New > Upload Plugin (or check for update notification)
  6. 6. Update to the latest version of BeeTeam368 Extensions (version 2.3.6 or later)
  7. 7. Verify the update was successful by confirming the new version number

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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