# CVE-2024-6647: Croogo Setting Theme unrestricted upload

> Attackers can upload malicious files via the theme setting handler in Croogo, potentially leading to remote code execution on unsupported installations.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-73wr-h9hv-jwjj

## What is CVE-2024-6647?

CVE-2024-6647 is a medium-severity vulnerability in Croogo, published on 10 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as critical has been found in Croogo up to 4.0.7. This affects an unknown part of the file admin/settings/settings/prefix/Theme of the component Setting Handler. The manipulation of the argument Content-Type leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-271053 was assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

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


## How do I fix CVE-2024-6647?

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

## Is CVE-2024-6647 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6647 and fix it if it is affected.

What it is: CVE-2024-6647 is a medium-severity vulnerability in Croogo, published on 10 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6647 exists.

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

## Sources

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

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