CVE-2026-4290

WP Travel Pro <= 11.1.0 - Missing Authorization to Unauthenticated Arbitrary User Deletion Including Administrators

2026-05-28 14:22
Ren Voza

Strategic Overview

Status
Patched in 11.2.0
Affected Plugin
WP Travel Pro
Affected Version
<= 11.1.0
CVSS
9.1Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-4290
View all WP Travel Pro vulnerabilities

At a glance

CVE-2026-4290 is a critical-severity Missing Authorization vulnerability in the WP Travel Pro WordPress plugin, affecting versions <= 11.1.0. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 11.2.0; sites on affected versions should update now. Disclosed May 2026, reported by Ren Voza.

Vulnerability Overview

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, 11.1.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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-862: Missing Authorization

WP Travel Pro <= 11.1.0 carries this weakness at check_permission(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Travel Pro the fix is 11.2.0: builds <= 11.1.0 are affected, anything from 11.2.0 onward is not.

Remediation

Update to version 11.2.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Travel Pro 11.2.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C