dbcve.org
VidmovWordPress extension · Beeteam368

CVE-2025-6381

HIGH · 8.8 CVSS v3.1 Published 2025-06-28
Fix available
A fix is available. Upgrade to 2.3.5 or later.
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 Directory Traversal in all versions up to, and including, 2.3.4 via the handle_remove_temp_file() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform actions on files outside of the originally intended directory. This vulnerability can be used to delete the wp-config.php file, which can be leveraged into a site takeover.

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 (versions up to 2.3.4) contains a directory traversal vulnerability in the handle_remove_temp_file() function. Authenticated attackers with Subscriber-level permissions can manipulate file paths to delete files outside the intended directory, notably wp-config.php, leading to site takeover.

MitigationUpdate the BeeTeam368 Extensions plugin to the latest patched version. If no patch is available, disable and remove the plugin until a fix is released.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VidmovWordPress extension
Affected:< 2.3.5

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. Verify if BeeTeam368 Extensions plugin is installed
    Check the WordPress plugins directory for the Beeteam368 plugin folder, or query the wp_plugins database table for plugin slugs containing 'beeteam368' or 'vidmov'
    Affected if Plugin folder exists in /wp-content/plugins/ with 'beeteam368' or 'vidmov' in the name
  2. Identify the exact installed version
    Read the main plugin PHP file header for 'Version:' value, or query wp_options for option_name containing 'beeteam368' version information
    Affected if Version is 2.3.4 or lower, or version field shows < 2.3.5
  3. Confirm plugin is active
    Query wp_options table for option_name = 'active_plugins' and check if the Beeteam368 plugin slug is present in the serialized array
    Affected if Plugin appears in the active_plugins option and is not deactivated
  4. Check for vulnerable function accessibility
    Review the plugin code for handle_remove_temp_file() function and verify it is hooked to an AJAX action (wp_ajax_) or frontend endpoint without capability checks beyond 'read'
    Affected if handle_remove_temp_file() is accessible to unauthenticated or Subscriber-level users
  5. Verify presence of low-privilege user accounts
    Query wp_users and wp_usermeta to list users with role 'subscriber' using SELECT u.user_login, u.user_email FROM wp_users u JOIN wp_usermeta m ON u.ID = m.user_id WHERE m.meta_key = 'wp_capabilities' AND m.meta_value LIKE '%subscriber%'
    Affected if Any Subscriber-level accounts exist in the database

User is affected if the BeeTeam368 Vidmov plugin version is 2.3.4 or lower AND the plugin is active AND the handle_remove_temp_file() function is accessible to users with Subscriber-level permissions.

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
Upgrade available Upgrade to 2.3.5 or later
Fixed in 2.3.5
Interim mitigation

Update the BeeTeam368 Extensions plugin to the latest patched version. If no patch is available, disable and remove the plugin until a fix is released.

Recommended fix High confidence

Plugin version 2.3.5

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the BeeTeam368 Extensions (Vidmov) plugin in the list
  4. 4. Click 'Update now' if an update to version 2.3.5 or higher is available, or manually upload version 2.3.5 from the WordPress plugin repository
  5. 5. After updating, verify the plugin version shows 2.3.5 or later in the Plugins list
  6. 6. Test that the site functionality remains intact
  7. 7. Consider using a file integrity scanner to confirm wp-config.php and other critical files remain unmodified

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

Fix this in Vidmov Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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