CVE-2026-13146

Travel <= 12.0.1 - Unauthenticated Insecure Direct Object Reference

Strategic Overview

Status
Patched in 12.0.2
Affected Version
<= 12.0.1
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-13146
View all WP Travel – Ultimate Travel Booking System, Tour Management Engine vulnerabilities

At a glance

CVE-2026-13146 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Travel WordPress plugin, affecting versions <= 12.0.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 12.0.2; sites on affected versions should update now. Disclosed September 2026, reported by Revanth Hari Narayana Matte.

Vulnerability Overview

The Travel plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 12.0.1. This is due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP Travel <= 12.0.1 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP Travel the fix is 12.0.2: builds <= 12.0.1 are affected, anything from 12.0.2 onward is not.

Remediation

Update to version 12.0.2, 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 12.0.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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