# CVE-2026-2025: Mail Mint < 1.19.5 - Unauthenticated Emails Disclosure

> Unauthenticated attackers can retrieve user email addresses via an unprotected REST API endpoint in the Mail Mint WordPress 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:** 4 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-rgg8-j3f4-j5pg

## What is CVE-2026-2025?

CVE-2026-2025 is a high-severity missing authorization vulnerability in Unknown Mail Mint, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mail Mint  WordPress plugin before 1.19.5 does not have authorization in one of its REST API endpoint, allowing unauthenticated users to call it and retrieve the email addresses of users on the blog

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-2025 being exploited?

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

Public exploit code:

- Mail Mint < 1.19.5 - Unauthenticated Email Disclosure (nuclei): http/cves/2026/CVE-2026-2025.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2025 is a high-severity missing authorization vulnerability in Unknown Mail Mint, published on 4 Mar 2026. 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-2026-2025 exists.

Affected product: Unknown Mail Mint. 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-2026-2025/ (Markdown: https://insights.sbomify.com/CVE-2026-2025/index.md)
```

## Sources

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

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