# CVE-2026-14925: Import WP < 2.14.23 - Unauthenticated Sensitive Information Exposure via Export File Download

> Unauthenticated attackers can download administrator-generated export files containing sensitive user data due to missing authorization checks in the Import WP 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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-q67g-v857-6748

## What is CVE-2026-14925?

CVE-2026-14925 is a high-severity missing authorization vulnerability in Unknown Import WP, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Import WP  WordPress plugin before 2.14.23 does not perform any authorization check on one of its export-file download handlers, allowing unauthenticated attackers to download export files generated by administrators, which may contain user personal data such as email addresses, login names and roles. Exploitation requires an unconsumed export to already exist and a low-entropy, time-based download key to be obtained.

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

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


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

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

## Is CVE-2026-14925 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14925 is a high-severity missing authorization vulnerability in Unknown Import WP, published on 12 Aug 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-14925 exists.

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

## Sources

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

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