# CVE-2023-4836: WordPress File Sharing Plugin < 2.0.5 - Subscriber+ Sensitive Data and Files Exposure via IDOR

> Attackers can access sensitive files and folders by manipulating IDs due to missing authorization checks in the WordPress File Sharing Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Oct 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-r75f-cj9v-2727

## What is CVE-2023-4836?

CVE-2023-4836 is a medium-severity missing authorization vulnerability in Unknown WordPress File Sharing Plugin, published on 31 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WordPress File Sharing Plugin WordPress plugin before 2.0.5 does not check authorization before displaying files and folders, allowing users to gain access to those filed by manipulating IDs which can easily be brute forced

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Userprivatefiles Wordpress File Sharing Plugin.

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

Upgrade to a fixed version.

## Is CVE-2023-4836 being exploited?

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

## Other vulnerabilities in Unknown WordPress File Sharing Plugin

- [CVE-2023-4636](https://insights.sbomify.com/CVE-2023-4636/): WordPress File Sharing Plugin <= 2.0.3 - Authenticated (Admin+) Stored Cross-Site Scripting (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4836 is a medium-severity missing authorization vulnerability in Unknown WordPress File Sharing Plugin, published on 31 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4836 exists.

Affected product: Unknown WordPress File Sharing Plugin. 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-4836/ (Markdown: https://insights.sbomify.com/CVE-2023-4836/index.md)
```

## Sources

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

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