# CVE-2022-0403: Library File Manager < 5.2.3 - Subscriber+ Arbitrary File Creation/Upload/Deletion

> Authenticated subscribers can upload arbitrary files due to missing authorization and CSRF checks in the Library File Manager plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6pvh-hm7g-3cc8

## What is CVE-2022-0403?

CVE-2022-0403 is a high-severity vulnerability in Unknown Library File Manager, published on 4 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Library File Manager WordPress plugin before 5.2.3 is using an outdated version of the elFinder library, which is know to be affected by security issues (CVE-2021-32682), and does not have any authorisation as well as CSRF checks in its connector AJAX action, allowing any authenticated users, such as subscriber to call it. Furthermore, as the options passed to the elFinder library does not restrict any file type, users with a role as low as subscriber can Create/Upload/Delete Arbitrary files and folders.

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

## Which versions are affected by CVE-2022-0403?

It affects 1 product.


Products: Wpjos Library File Manager.

## How do I fix CVE-2022-0403?

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

## Is CVE-2022-0403 being exploited?

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

## Other vulnerabilities in Unknown Library File Manager

- [CVE-2017-20091](https://insights.sbomify.com/CVE-2017-20091/): File Manager Plugin cross-site request forgery (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0403 and fix it if it is affected.

What it is: CVE-2022-0403 is a high-severity vulnerability in Unknown Library File Manager, published on 4 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0403 in the wild and no public exploit code.

Affected product: Unknown Library File Manager. 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-2022-0403/ (Markdown: https://insights.sbomify.com/CVE-2022-0403/index.md)
```

## Sources

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

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