CVE-2026-27089

Travelly – Tour & Travel Booking Manager for WooCommerce | Tour & Hotel Booking Solution <= 2.1.7 - Missing Authorization

2026-06-01 00:00
benzdeus

Strategic Overview

Status
Patched in 2.1.8
Affected Plugin
Travelly – Tour & Travel Booking Manager for WooCommerce
Affected Version
<= 2.1.7
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-27089
View all Travelly – Tour & Travel Booking Manager for WooCommerce vulnerabilities

At a glance

CVE-2026-27089 is a medium-severity Missing Authorization vulnerability in the Travelly WordPress plugin, affecting versions <= 2.1.7. 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 2.1.8; sites on affected versions should update now. Disclosed June 2026, reported by benzdeus.

Vulnerability Overview

The Travelly – Tour & Travel Booking Manager for WooCommerce | Tour & Hotel Booking Solution plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 2.1.7. 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-862: Missing Authorization

Reaching this weakness in Travelly <= 2.1.7 takes a caller who can reach the endpoint. 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 Travelly the fix is 2.1.8: builds <= 2.1.7 are affected, anything from 2.1.8 onward is not.

Remediation

Update to version 2.1.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Travelly 2.1.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-27089https://www.wordfence.com/threat-intel/vulnerabilities/id/6dd2b375-546c-45bf-b4f0-55b73152a6adhttps://nvd.nist.gov/vuln/detail/CVE-2026-27089

Related records

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