# CVE-2024-30162: File upload in n/a

> Admin users can upload malicious ZIP files to execute arbitrary PHP code on the server due to insufficient validation in the editor toolbar module.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-hccj-9v6g-qxjv

## What is CVE-2024-30162?

CVE-2024-30162 is a high-severity vulnerability in n/a, published on 7 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Invision Community through 4.7.16 allows remote code execution via the applications/core/modules/admin/editor/toolbar.php IPS\core\modules\admin\editor\_toolbar::addPlugin() method. This method handles uploaded ZIP files that are extracted into the applications/core/interface/ckeditor/ckeditor/plugins/ directory without properly verifying their content. This can be exploited by admin users (with the toolbar_manage permission) to write arbitrary PHP files into that directory, leading to execution of arbitrary PHP code in the context of the web server user.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2024-30162 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30162 is a high-severity vulnerability in n/a, published on 7 Jun 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-30162 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-30162/ (Markdown: https://insights.sbomify.com/CVE-2024-30162/index.md)
```

## Sources

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

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