CVE-2025-6379: The BeeTeam368 Extensions Pro plugin for WordPress is vulnerable to Directory Traversal in all versions up to,

Q: How do I fix CVE-2025-6379?

vidmov: upgrade to 2.3.5. Exact commands for each OS are on this page.

Q: Is CVE-2025-6379 being exploited?

CVE-2025-6379 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-6379 affect?

CVE-2025-6379 affects vidmov. Severity is high (CVSS 8.8). The 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

This month

HIGH 8.8UPGRADE

CVE-2025-6379 is a high-severity flaw (CVSS 8.8) affecting vidmov. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The 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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 45%)
CISA exploited list	No
Weakness	CWE-22
Published	2025-06-28
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: beeteam368

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-28 04:15 UTCPublished CVE record published
2026-06-17 10:01 UTCUpdated Record last modified

beeteam368 vidmov UPGRADE

Affected: < 2.3.5

Fixed in: 2.3.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vidmov || rpm -q vidmov || vidmov --version

2. UPGRADE to 2.3.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vidmov

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vidmov

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-6379?

vidmov: upgrade to 2.3.5. Exact commands for each OS are on this page.

Is CVE-2025-6379 being exploited?

CVE-2025-6379 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-6379 affect?

CVE-2025-6379 affects vidmov. Severity is high (CVSS 8.8). The 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

How urgent is CVE-2025-6379?

Priority 44/100. High severity

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2025-6381 HIGH 8.8 UPGRADE The BeeTeam368 Extensions plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and

References

← Back to latest CVEs