# CVE-2023-4930: Front End PM < 11.4.3 - Sensitive Data Exposure via Directory Listing

> Unauthenticated attackers can list and download private message attachments if the web server's autoindex feature is enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-p7f5-95m3-2fw7

## What is CVE-2023-4930?

CVE-2023-4930 is a medium-severity vulnerability in Unknown Front End PM, published on 6 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Front End PM WordPress plugin before 11.4.3 does not block listing the contents of the directories where it stores attachments to private messages, allowing unauthenticated visitors to list and download private attachments if the autoindex feature of the web server is enabled.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


Products: Shamimsplugins Front End Pm.

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

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

## Is CVE-2023-4930 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4930 is a medium-severity vulnerability in Unknown Front End PM, published on 6 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4930 exists.

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

## Sources

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

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