Summary
CVE-2026-27089 is a high-severity Unauthenticated Bypass vulnerability (CWE-290: Authentication Bypass by Spoofing) in the WpTravelly plugin for WordPress, developed by Magepeople Inc. It affects all versions up to and including 2.1.7 and carries a CVSS v3.1 base score of 7.5 (HIGH). The flaw allows unauthenticated remote attackers to circumvent the plugin’s authentication and authorization controls, resulting in a HIGH integrity impact — meaning unauthorized modification of site data is possible without any valid credentials or user interaction.
Technical details
- Root cause: The vulnerability is classified as CWE-290 (Authentication Bypass by Spoofing), meaning the plugin fails to adequately verify the identity or authorization of a requestor, allowing an unauthenticated actor to satisfy authentication checks through a spoofed or forged request.
- Attack vector: Fully remote and unauthenticated — exploitable over the network with no privileges and no user interaction required (AV:N/AC:L/PR:N/UI:N).
- Impact: HIGH integrity impact (I:H); no confidentiality or availability impact. Successful exploitation enables unauthorized write-level actions against the affected WordPress site — such as manipulating tour listings, booking data, or other plugin-controlled content — without any valid account.
- Pattern of access-control weaknesses: Public vulnerability databases record multiple prior authorization flaws in this plugin, including broken access control (CVE-2024-43212, CVE-2026-27331), PHP object injection (CVE-2025-30892), and local file inclusion (CVE-2025-30891), reflecting a recurring pattern of insufficient access controls across plugin versions.
- Discovery: Reported by security researcher benzdeus and published June 15, 2026.
Affected software
- WpTravelly (tour-booking-manager) by Magepeople Inc. — all versions ≤ 2.1.7
Severity
- CVSS v3.1 Base Score: 7.5 (HIGH)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Mitigation and recommended actions
- Immediate: Update WpTravelly to version 2.1.8 or later (current version is 2.1.9). The fix was first introduced in version 2.1.8.
- Administrators who cannot immediately upgrade should consider restricting access to WordPress AJAX endpoints associated with the plugin (
ttbm_ajax_url) at the web server or WAF level as a temporary measure until the plugin is updated. - Review recent unauthorized changes to tour listings, bookings, or site content on affected installations.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

