# CVE-2025-32164: WordPress m1.DownloadList plugin <= 0.24 - Sensitive Data Exposure vulnerability

> An attacker can retrieve embedded sensitive system data from the m1.DownloadList WordPress plugin, exposing confidential information to unauthorized users.

- **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:** 8 Apr 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7wj9-rggf-4prj

## What is CVE-2025-32164?

CVE-2025-32164 is a medium-severity vulnerability in maennchen1.de m1.DownloadList, published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in maennchen1.de m1.DownloadList m1downloadlist allows Retrieve Embedded Sensitive Data.This issue affects m1.DownloadList: from n/a through <= 0.24.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2025-32164?


## How do I fix CVE-2025-32164?

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

## Is CVE-2025-32164 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32164 and fix it if it is affected.

What it is: CVE-2025-32164 is a medium-severity vulnerability in maennchen1.de m1.DownloadList, published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32164 in the wild and no public exploit code.

Affected product: maennchen1.de m1.DownloadList. 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-2025-32164/ (Markdown: https://insights.sbomify.com/CVE-2025-32164/index.md)
```

## Sources

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

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