{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6379 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6379 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6379 is a high-severity path traversal vulnerability in BeeTeam368 Extensions Pro, published on 28 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6379 and fix it if it is affected.\n\nWhat it is: CVE-2025-6379 is a high-severity path traversal vulnerability in BeeTeam368 Extensions Pro, published on 28 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6379 in the wild and no public exploit code.\n\nAffected product: BeeTeam368 Extensions Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-6379/ (Markdown: https://insights.sbomify.com/CVE-2025-6379/index.md)","id":"CVE-2025-6379","markdown":"https://insights.sbomify.com/CVE-2025-6379/index.md","name":"CVE-2025-6379","record":{"aliases":["GHSA-g5fj-m9hm-fjc2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can delete arbitrary files, including wp-config.php, leading to site takeover in BeeTeam368 Extensions Pro.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"vidmov","vendor":"beeteam368"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"BeeTeam368 Extensions Pro \u003c= 2.3.4 - Authenticated (Subscriber+) Directory Traversal to Arbitrary File Deletion","id":"CVE-2025-6379","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"ONLYOFFICE Docs 1.1.0 - 2.2.0 - Missing Authorization to Unauthenticated Privilege Escalation via callback Function","id":"CVE-2025-6380"},"packages":[],"prev":{"headline":"Cross-site scripting in Responsive Food and Drink Menu","id":"CVE-2025-6378"},"products":["BeeTeam368 Extensions Pro"],"published":"2025-06-28","related":[{"cvss_score":8.8,"headline":"BeeTeam368 Extensions \u003c= 2.3.4 - Authenticated (Subscriber+) Directory Traversal to Arbitrary File Deletion","id":"CVE-2025-6381","kev_date_added":null,"published":"2025-06-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["beeteam368"]},"summary":"Authenticated attackers can delete arbitrary files, including wp-config.php, leading to site takeover in BeeTeam368 Extensions Pro.","url":"https://insights.sbomify.com/CVE-2025-6379/"}