# CVE-2026-104757: WordPress Import and export users and customers plugin <= 2.5.5 - Privilege Escalation vulnerability

> An editor can escalate privileges in the Import and export users and customers WordPress plugin, allowing unauthorized access to higher-level administrative functions.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-vhhj-fj85-qr7v

## What is CVE-2026-104757?

CVE-2026-104757 is a high-severity vulnerability in Javier Carazo Import and export users and customers, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Editor Privilege Escalation in Import and export users and customers <= 2.5.5 versions.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-104757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104757 is a high-severity vulnerability in Javier Carazo Import and export users and customers, published on 6 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104757 in the wild and no public exploit code.

Affected product: Javier Carazo Import and export users and customers. 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-104757/ (Markdown: https://insights.sbomify.com/CVE-2026-104757/index.md)
```

## Sources

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

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