# CVE-2024-32418: Code injection in n/a

> Remote attackers can execute arbitrary code in flusity CMS via the add_addon.php component, posing a critical risk to site integrity.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 22 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-2pvq-77pm-76c4

## What is CVE-2024-32418?

CVE-2024-32418 is a critical code injection vulnerability in n/a, published on 22 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in flusity CMS v2.33 allows a remote attacker to execute arbitrary code via the add_addon.php component.

Weakness: CWE-284 (Improper Access Control), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Flusity Flusity.

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

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

## Is CVE-2024-32418 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-31666](https://insights.sbomify.com/CVE-2024-31666/): Code injection in n/a (critical 9.8)
- [CVE-2024-25502](https://insights.sbomify.com/CVE-2024-25502/): Path traversal in n/a (critical 9.8)
- [CVE-2024-23094](https://insights.sbomify.com/CVE-2024-23094/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-26350](https://insights.sbomify.com/CVE-2024-26350/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-26352](https://insights.sbomify.com/CVE-2024-26352/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32418 is a critical code injection vulnerability in n/a, published on 22 Apr 2024. 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-2024-32418 exists.

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

## Sources

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

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