How severe is CVE-2025-6381?

CVE-2025-6381 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-6381 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-6381?

CVE-2025-6381 affects Beeteam368 Vidmov. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-6381?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-6381 have an EU (EUVD) identifier?

Yes. CVE-2025-6381 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-28733.

When was CVE-2025-6381 published?

CVE-2025-6381 was published on 2025-06-28 and last updated on 2026-06-17.

CVE-2025-6381

CVE-2025-6381 is a high-severity vulnerability in Beeteam368 Vidmov with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-36.

Key facts

Severity: High (CVSS 3.x base score 8.8)
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-28733
Weakness: CWE-36
Affected product: Beeteam368 Vidmov
Published: 2025-06-28
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-6381?: 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.
How severe is CVE-2025-6381?: CVE-2025-6381 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-6381 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-6381?: CVE-2025-6381 affects Beeteam368 Vidmov. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-6381?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-6381 have an EU (EUVD) identifier?: Yes. CVE-2025-6381 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-28733.
When was CVE-2025-6381 published?: CVE-2025-6381 was published on 2025-06-28 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:beeteam368:vidmov:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Beeteam368 Vidmov

CVE-2025-6379 — High (CVSS 8.8): The BeeTeam368 Extensions Pro plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and…

All CVEs affecting Beeteam368 Vidmov →

Other CWE-36 vulnerabilities

CVE-2023-3765 — Critical (CVSS 10.0): Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
CVE-2025-34392 — Critical (CVSS 9.8): Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not verify the URL…
CVE-2025-0851 — Critical (CVSS 9.8): A path traversal issue in ZipUtils.unzip and TarUtils.untar in Deep Java Library (DJL) on all platforms allows a bad…
CVE-2024-13161 — Critical (CVSS 9.8): Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security…
CVE-2024-13160 — Critical (CVSS 9.8): Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security…
CVE-2024-13159 — Critical (CVSS 9.8): Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security…

Browse all CWE-36 vulnerabilities →