# CVE-2026-12240: Deserialization in Export User Data

> Authenticated attackers can trigger arbitrary file deletion via PHP object injection in the Export User Data plugin, potentially leading to remote code execution.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-ww5c-p3qw-8xxf

## What is CVE-2026-12240?

CVE-2026-12240 is a high-severity unsafe deserialization vulnerability in qlstudio Export User Data, published on 30 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Export User Data plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the unserialize function in all versions up to, and including, 2.2.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Successful exploitation requires an administrator to trigger a user data export while a subscriber-level (or higher) user has stored a crafted serialized XLSXWriter object payload as their display name.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-12240 being exploited?

There is no known exploitation of CVE-2026-12240 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12240 is a high-severity unsafe deserialization vulnerability in qlstudio Export User Data, published on 30 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-12240 in the wild and no public exploit code.

Affected product: qlstudio Export User Data. 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-12240/ (Markdown: https://insights.sbomify.com/CVE-2026-12240/index.md)
```

## Sources

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

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