# CVE-2025-15264: FeehiCMS TimThumb timthumb.php server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in FeehiCMS's TimThumb component via the src argument.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 30 Dec 2025
- **Also known as:** GHSA-4g6x-74c2-rfr9

## What is CVE-2025-15264?

CVE-2025-15264 is a medium-severity server-side request forgery vulnerability in FeehiCMS, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in FeehiCMS up to 2.1.1. Impacted is an unknown function of the file frontend/web/timthumb.php of the component TimThumb. Executing manipulation of the argument src can lead to server-side request forgery. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Feehi Feehicms.

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

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

## Is CVE-2025-15264 being exploited?

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

## Other vulnerabilities in FeehiCMS

- [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-65657](https://insights.sbomify.com/CVE-2025-65657/): FeehiCMS Has a Remote Code Execution via Unrestricted File Upload in Ad Management (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15264 is a medium-severity server-side request forgery vulnerability in FeehiCMS, published on 30 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-15264 exists.

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

## Sources

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

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