# CVE-2026-4290: WP Travel Pro <= 10.6.0 - Missing Authorization to Unauthenticated Arbitrary User Deletion Including Administrators

> Unauthenticated attackers can delete arbitrary user accounts, including administrators, due to missing authorization checks in the WP Travel Pro plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-3r5v-r3c5-jj73

## What is CVE-2026-4290?

CVE-2026-4290 is a critical missing authorization vulnerability in WPTravel WP Travel Pro, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Travel Pro plugin for WordPress is vulnerable to arbitrary user deletion via the /wp-json/wp-travel/v1/travel-guide/{user_id} REST API endpoint in all versions up to, and including, 10.6.0. This is due to the check_permission() callback unconditionally returning true and the Database::delete() method passing the user ID directly to wp_delete_user() without any role validation. This makes it possible for unauthenticated attackers to delete arbitrary user accounts, including those of administrators.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-4290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4290 is a critical missing authorization vulnerability in WPTravel WP Travel Pro, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4290 in the wild and no public exploit code.

Affected product: WPTravel WP Travel Pro. 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-4290/ (Markdown: https://insights.sbomify.com/CVE-2026-4290/index.md)
```

## Sources

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

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