# CVE-2025-25174: WordPress BeeTeam368 Extensions Plugin <= 1.9.4 - Local File Inclusion Vulnerability

> Attackers can exploit a local file inclusion vulnerability in the BeeTeam368 Extensions plugin to read sensitive files or execute arbitrary code.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-6c46-h43m-27v5

## What is CVE-2025-25174?

CVE-2025-25174 is a critical path traversal vulnerability in BeeTeam368 Extensions, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2025-25174?


## How do I fix CVE-2025-25174?

No fix has been published for CVE-2025-25174 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-25174 being exploited?

There is no known exploitation of CVE-2025-25174 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25174 and fix it if it is affected.

What it is: CVE-2025-25174 is a critical path traversal vulnerability in BeeTeam368 Extensions, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25174 in the wild and no public exploit code.

Affected product: BeeTeam368 Extensions. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-25174/ (Markdown: https://insights.sbomify.com/CVE-2025-25174/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25174
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25174
- OSV: https://osv.dev/vulnerability/CVE-2025-25174

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-25174/
Summaries are generated and may contain mistakes; the official description above is the record.