VidmovWordPress extension · Beeteam368
CVE-2025-6379
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 · uneditedThe BeeTeam368 Extensions Pro plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.3.4 via the handle_live_fn() 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 confidenceThe BeeTeam368 Extensions Pro WordPress plugin has a directory traversal vulnerability in the handle_live_fn() function. Authenticated attackers with Subscriber-level access or higher can manipulate file paths to access or delete files outside the intended directory, specifically targeting wp-config.php for site takeover.
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
< 2.3.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Beeteam368 Vidmov plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and look for 'Beeteam368 Vidmov' or check the wp-content/plugins/ directory for a folder containing 'vidmov' or 'beeteam368'Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn the Plugins list, find Beeteam368 Vidmov and note the version number displayed under the plugin name, or open the main plugin PHP file and locate the 'Version' header in the plugin comment blockAffected if Version is less than 2.3.5 (e.g., 2.3.4, 2.3.3, etc.)
-
Determine if authenticated access existsIn WordPress admin, go to Users and review the user list to see if any users with Subscriber, Contributor, Author, Editor, or Administrator roles existAffected if At least one user with Subscriber-level access or higher is present in the system
Your environment is affected if the Beeteam368 Vidmov plugin version is below 2.3.5 and any authenticated user with Subscriber-level or higher access exists in WordPress.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.3.5
Update the BeeTeam368 Extensions Pro plugin to a version beyond 2.3.4. If no patched version is available, disable or remove the plugin until a fix is released.
Vidmov version 2.3.5
- Log in to the WordPress admin dashboard
- Navigate to Dashboard > Updates or Appearance > Themes (depending on how Vidmov is installed)
- Check for the Vidmov theme update
- Update to version 2.3.5
- Verify the update completed successfully
- Confirm the handle_live_fn() function no longer allows path traversal
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vidmov
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6379 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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