# CVE-2025-10638: NS Maintenance Mode for WP <= 1.3.1 - Unauthenticated Subscribers Export

> Unauthenticated attackers can download subscriber lists containing names and emails due to missing authorization in the export function.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 22 Oct 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-f6x3-5ffg-hff5

## What is CVE-2025-10638?

CVE-2025-10638 is a medium-severity missing authorization vulnerability in Unknown NS Maintenance Mode for WP, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NS Maintenance Mode for WP WordPress plugin through 1.3.1 lacks authorization in its subscriber export function allowing unauthenticated attackers to download a list of a site's subscribers containing their name and email address

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


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

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

## Is CVE-2025-10638 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10638 is a medium-severity missing authorization vulnerability in Unknown NS Maintenance Mode for WP, published on 22 Oct 2025. 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-2025-10638 exists.

Affected product: Unknown NS Maintenance Mode for WP. 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-10638/ (Markdown: https://insights.sbomify.com/CVE-2025-10638/index.md)
```

## Sources

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

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