# CVE-2026-5335: Magic Export & Import < 1.2.0 - Unauthenticated PII Disclosure

> Unauthenticated attackers can access publicly stored CSV files to leak sensitive user information from the Magic Export & Import WordPress plugin.

- **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:** 4 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-v3f4-pgv5-qqhc

## What is CVE-2026-5335?

CVE-2026-5335 is a medium-severity vulnerability in Unknown Magic Export & Import, published on 4 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Magic Export & Import WordPress plugin before 1.2.0 stores exported CSV files at a publicly accessible location, making it possible for any visitors to leak sensitive user information.

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

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


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

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

## Is CVE-2026-5335 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5335 is a medium-severity vulnerability in Unknown Magic Export & Import, published on 4 May 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-5335 exists.

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

## Sources

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

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