# CVE-2026-14849: Paid Member Subscriptions < 3.0.7 - Unauthenticated Sensitive Information Exposure via Residual Export Files

> Unauthenticated attackers can download sensitive member and payment data from predictable export files in the uploads directory.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/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:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-wv4h-qxh7-5899

## What is CVE-2026-14849?

CVE-2026-14849 is a low-severity vulnerability in Unknown Paid Membership Subscriptions, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Paid Membership Subscriptions  WordPress plugin before 3.0.7 does not protect the member and payment export files it writes to a predictable location in the uploads directory, allowing unauthenticated users to download the exported member and payment data (including PII) while an export artifact is present.

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

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


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

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

## Is CVE-2026-14849 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14849 is a low-severity vulnerability in Unknown Paid Membership Subscriptions, published on 31 Jul 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-14849 exists.

Affected product: Unknown Paid Membership Subscriptions. 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-14849/ (Markdown: https://insights.sbomify.com/CVE-2026-14849/index.md)
```

## Sources

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

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