# CVE-2023-6505: Prime Mover < 1.9.3 - Directory Listing to Sensitive Data Exposure

> An attacker can access sensitive export files via directory listing in the Migrate WordPress Website & Backups plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 8 Jan 2024
- **Updated:** 18 Jun 2025
- **Also known as:** GHSA-2g38-fxhq-9w3p

## What is CVE-2023-6505?

CVE-2023-6505 is a high-severity vulnerability in Unknown Migrate WordPress Website & Backups, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Migrate WordPress Website & Backups WordPress plugin before 1.9.3 does not prevent directory listing in sensitive directories containing export files.

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

It affects 1 product.


Products: Codexonics Prime Mover.

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

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

## Is CVE-2023-6505 being exploited?

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

Public exploit code:

- Prime Mover < 1.9.3 - Sensitive Data Exposure (nuclei): http/cves/2023/CVE-2023-6505.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6505 is a high-severity vulnerability in Unknown Migrate WordPress Website & Backups, published on 8 Jan 2024. 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-6505 exists.

Affected product: Unknown Migrate WordPress Website & Backups. 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-6505/ (Markdown: https://insights.sbomify.com/CVE-2023-6505/index.md)
```

## Sources

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

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