# CVE-2023-53869: WEBIGniter 28.7.23 Unrestricted File Upload Remote Code Execution

> Authenticated attackers can upload malicious PHP files via the media function to achieve remote code execution on the WebIGniter server.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 15 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-r46w-6r25-mwj8

## What is CVE-2023-53869?

CVE-2023-53869 is a high-severity vulnerability in WebIGniter, published on 15 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WEBIGniter 28.7.23 contains a file upload vulnerability that allows authenticated attackers to upload and execute dangerous PHP files through the media function. Attackers can leverage any created account to upload malicious PHP scripts that enable remote code execution on the application server.

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

## Which versions are affected by CVE-2023-53869?


## How do I fix CVE-2023-53869?

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

## Is CVE-2023-53869 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53869 and fix it if it is affected.

What it is: CVE-2023-53869 is a high-severity vulnerability in WebIGniter, published on 15 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53869 in the wild and no public exploit code.

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

## Sources

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

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