# CVE-2024-8295: FeehiCMS index.php createBanner unrestricted upload

> Attackers can upload malicious files via the banner creation feature in FeehiCMS, potentially leading to remote code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-3wrg-6mg5-jg2v

## What is CVE-2024-8295?

CVE-2024-8295 is a medium-severity vulnerability in FeehiCMS, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in FeehiCMS up to 2.1.1 and classified as critical. This vulnerability affects the function createBanner of the file /admin/index.php?r=banner%2Fbanner-create. The manipulation of the argument BannerForm[img] leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-8295?

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-2024-8295?

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

## Is CVE-2024-8295 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8295 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-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-2024-8295 and fix it if it is affected.

What it is: CVE-2024-8295 is a medium-severity vulnerability in FeehiCMS, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8295 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-2024-8295/ (Markdown: https://insights.sbomify.com/CVE-2024-8295/index.md)
```

## Sources

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

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