dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4290

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Travel Pro plugin for WordPress contains an insecure REST API endpoint at /wp-json/wp-travel/v1/travel-guide/{user_id} that allows unauthenticated attackers to delete arbitrary user accounts. The vulnerability results from two compounding issues: a check_permission() callback that unconditionally returns true, bypassing authentication entirely, and Database::delete() passing the user ID directly to wp_delete_user() without any role validation, enabling deletion of administrator accounts.

MitigationUpdate WP Travel Pro to a patched version as soon as available. Until then, disable the plugin or restrict access to the wp-travel REST API endpoints at the server level (e.g., via .htaccess or firewall rules).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Travel Pro plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Travel Pro' or check the file system for the plugin directory at /wp-content/plugins/
    Affected if The WP Travel Pro plugin is present and active on the WordPress site
  2. Confirm the vulnerable REST API endpoint is accessible
    Send a GET request to /wp-json/wp-travel/v1/travel-guide/1 using a tool like curl or Burp Suite without providing any authentication headers
    Affected if The endpoint returns an HTTP 200 response instead of 401 Unauthorized or 403 Forbidden, indicating the endpoint is reachable without credentials
  3. Test if the user deletion function is callable via the API
    Send a DELETE request to /wp-json/wp-travel/v1/travel-guide/{user_id} where {user_id} is a valid user ID on the site, without authentication headers
    Affected if The request succeeds with HTTP 200 and the specified user is actually deleted from the WordPress database, confirming the vulnerability is exploitable
  4. Audit recent user account deletions
    In WordPress admin, go to Users > All Users and review the user list for any unexpected deletions, or query the wp_usermeta table for recent changes to user roles or the wp_users table for deleted accounts
    Affected if Users have been deleted, especially administrative accounts, that were not intentionally removed by legitimate administrators

A user is affected if the WP Travel Pro plugin is active and the /wp-json/wp-travel/v1/travel-guide/{user_id} endpoint is accessible without authentication, allowing unauthenticated attackers to delete any user account.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Travel Pro to a patched version as soon as available. Until then, disable the plugin or restrict access to the wp-travel REST API endpoints at the server level (e.g., via .htaccess or firewall rules).

Recommended fix Moderate confidence

WP Travel Pro 10.7.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP Travel Pro plugin
  4. Check the current installed version (should be 10.6.0 or below if vulnerable)
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Verify the update completed successfully
  7. Confirm the new version number after update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation5.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4290 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data