# CVE-2025-65657: FeehiCMS Has a Remote Code Execution via Unrestricted File Upload in Ad Management

> Authenticated attackers can upload malicious PHP files in FeehiCMS to achieve remote code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-mcxq-54f4-mmx5

## What is CVE-2025-65657?

CVE-2025-65657 is a medium-severity vulnerability in n/a, published on 2 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FeehiCMS version 2.1.1 has a Remote Code Execution via Unrestricted File Upload in Ad Management. FeehiCMS version 2.1.1 allows authenticated remote attackers to upload files that the server later executes (or stores in an executable location) without sufficient validation, sanitization, or execution restrictions. An authenticated remote attacker can upload a crafted PHP file and cause the application or web server to execute it, resulting in remote code execution (RCE).

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

2 open source packages ship an affected version, including feehi/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `feehi/cms` | Packagist | All versions to 2.1.1 | None |
| `feehi/cms` | Packagist | All versions to 2.1.1 | None |

Products: Feehi Feehicms.

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

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

## Is CVE-2025-65657 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65657 exists.

## Other vulnerabilities in n/a

- [CVE-2020-21174](https://insights.sbomify.com/CVE-2020-21174/): liufee CMS File Upload vulnerability (critical 9.8)
- [CVE-2020-21489](https://insights.sbomify.com/CVE-2020-21489/): Liufee CMS File Upload vulnerability (critical 9.8)
- [CVE-2020-21516](https://insights.sbomify.com/CVE-2020-21516/): FeehiCMS has an arbitrary file upload vulnerability (critical 9.8)
- [CVE-2020-21322](https://insights.sbomify.com/CVE-2020-21322/): Arbitrary Code Execution in feehi/cms (critical 9.8)
- [CVE-2025-15264](https://insights.sbomify.com/CVE-2025-15264/): FeehiCMS TimThumb timthumb.php server-side request forgery (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65657 is a medium-severity vulnerability in n/a, published on 2 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65657 exists.

Affected packages and fixed versions:
- feehi/cms (Packagist): affected all versions up to 2.1.1; no fix listed
- feehi/cms (Packagist): affected all versions up to 2.1.1; no fix listed

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-65657/ (Markdown: https://insights.sbomify.com/CVE-2025-65657/index.md)
```

## Sources

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

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