# CVE-2024-8031: Secure Downloads < 1.2.3 - Admin+ Arbitrary File Download

> Authenticated admins can download arbitrary files, including sensitive configuration files, due to improper file access restrictions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** No
- **Published:** 15 May 2025
- **Updated:** 17 May 2025
- **Also known as:** GHSA-p8rv-v842-xwm4

## What is CVE-2024-8031?

CVE-2024-8031 is a medium-severity path traversal vulnerability in Unknown Secure Downloads, published on 15 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Secure Downloads WordPress plugin before 1.2.3 is vulnerable does not properly restrict which files can be downloaded. This makes it possible for authenticated attackers, with admin-level access and above, to download arbitrary files that may contain sensitive information like wp-config.php.

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

## Which versions are affected by CVE-2024-8031?

It affects 1 product.


Products: Wpbookingcalendar Secure Downloads.

## How do I fix CVE-2024-8031?

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

## Is CVE-2024-8031 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8031 and fix it if it is affected.

What it is: CVE-2024-8031 is a medium-severity path traversal vulnerability in Unknown Secure Downloads, published on 15 May 2025. 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-2024-8031 exists.

Affected product: Unknown Secure Downloads. 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-2024-8031/ (Markdown: https://insights.sbomify.com/CVE-2024-8031/index.md)
```

## Sources

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

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