# CVE-2023-5762: Filr – Secure document library < 1.2.3.6 - Author+ RCE via file upload with phar ext

> An attacker with Author privileges can achieve remote code execution by uploading a malicious file, compromising the server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 4 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-wpgp-69jp-wj64

## What is CVE-2023-5762?

CVE-2023-5762 is a high-severity vulnerability in Unknown Filr, published on 4 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Filr WordPress plugin before 1.2.3.6 is vulnerable from an RCE (Remote Code Execution) vulnerability, which allows the operating system to execute commands and fully compromise the server on behalf of a user with Author-level privileges.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Filr Project Filr.

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

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

## Is CVE-2023-5762 being exploited?

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

## Other vulnerabilities in Unknown Filr

- [CVE-2022-1777](https://insights.sbomify.com/CVE-2022-1777/): Filr - Secure Document Library < 1.2.2.1 - Subscriber+ AJAX Calls (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5762 is a high-severity vulnerability in Unknown Filr, published on 4 Dec 2023. 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-5762 in the wild and no public exploit code.

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

## Sources

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

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