# CVE-2018-16352: File upload in n/a

> Attackers can upload malicious PHP code disguised as PNG images to WeaselCMS, leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 2 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-83p2-3vfv-j3jp

## What is CVE-2018-16352?

CVE-2018-16352 is a critical vulnerability in n/a, published on 2 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a PHP code upload vulnerability in WeaselCMS 0.3.6 via index.php because code can be embedded at the end of a .png file when the image/png content type is used.

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

## Which versions are affected by CVE-2018-16352?

It affects 1 product.


Products: Weaselcms Project Weaselcms.

## How do I fix CVE-2018-16352?

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

## Is CVE-2018-16352 being exploited?

There is no known exploitation of CVE-2018-16352 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-14958](https://insights.sbomify.com/CVE-2018-14958/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-14959](https://insights.sbomify.com/CVE-2018-14959/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-17361](https://insights.sbomify.com/CVE-2018-17361/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-14877](https://insights.sbomify.com/CVE-2018-14877/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16352 and fix it if it is affected.

What it is: CVE-2018-16352 is a critical vulnerability in n/a, published on 2 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16352 in the wild and no public exploit code.

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-2018-16352/ (Markdown: https://insights.sbomify.com/CVE-2018-16352/index.md)
```

## Sources

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

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