Skip to main content

WpTravelly CVE-2026-27089

| EUVDEUVD-2026-36914 HIGH
Authentication Bypass by Spoofing (CWE-290)
2026-06-15 Patchstack GHSA-g5vh-j4v8-x58p
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Fingerprint WordPress site running WpTravelly
  2. Delivery
    Identify vulnerable plugin endpoint
  3. Exploit
    Send crafted unauthenticated request
  4. Execution
    Bypass authentication check
  5. Impact
    Tamper with booking or tour data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Anti-spoofing controls
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Target WordPress site must have the MagePeople WpTravelly (Tour Booking Manager) plugin installed and active at version 2.1.7 or earlier, with the affected plugin endpoint reachable over HTTP/HTTPS from the attacker. Per CVSS AV:N/AC:L/PR:N/UI:N, no authentication, no user interaction, and no non-default configuration are required - exploitation works against default installs. Limiting factors are narrow: the attack only impacts integrity (C:N/A:N), so it does not directly yield data exfiltration or denial of service, and sites that have removed or disabled the plugin, or that gate /wp-admin and plugin AJAX/REST endpoints behind IP allowlists or a WAF rule covering this CVE, are not exposed.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N (7.5 High) indicates network-reachable, low-complexity, fully unauthenticated exploitation with high integrity impact but no confidentiality or availability loss - consistent with an action-level auth bypass that lets attackers modify or create records but not directly dump data or crash the service. EPSS data was not supplied in the input, so quantitative probability of exploitation cannot be cited. The vulnerability is not listed in CISA KEV and no public PoC is referenced by Patchstack at this time, so exploitation pressure is currently lower than the CVSS suggests; however, WordPress plugin auth bypasses are historically rapidly weaponized once a Patchstack advisory is public, so the real-world risk should be treated as elevated for any internet-exposed install.

Exploit ScenarioDerived

An attacker discovers a WordPress site running WpTravelly ≤ 2.1.7 via plugin fingerprinting, then sends a crafted HTTP request to an affected plugin endpoint that omits or forges authentication tokens. The server accepts the request as if from a privileged user and the attacker manipulates bookings, tour data, or other integrity-sensitive records without ever logging in. No public PoC is referenced in the supplied data, but the AC:L/PR:N/UI:N vector indicates exploitation is straightforward once the vulnerable endpoint is identified.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 15, 2026

Authentication bypass in the MagePeople WpTravelly WordPress plugin through version 2.1.7 allows remote unauthenticated attackers to circumvent identity verification and tamper with integrity-protected data. The flaw, reported by Patchstack and tracked as EUVD-2026-36914, is a CWE-290 Authentication Bypass by Spoofing impacting tour booking workflows on any WordPress site running the affected plugin. No public exploit identified at time of analysis, but the network-reachable, no-interaction attack vector elevates urgency for site operators.

RemediationAI

Upgrade the WpTravelly plugin to a version newer than 2.1.7 as published by MagePeople Inc.; no vendor-released patched version is independently confirmed in the supplied data, so administrators should consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/tour-booking-manager/vulnerability/wordpress-wptravelly-plugin-2-1-7-bypass-vulnerability-vulnerability for the fixed release identifier before applying. Until a confirmed fixed version is installed, compensating controls include deactivating the WpTravelly plugin entirely (trade-off: tour booking functionality goes offline), restricting access to wp-admin/admin-ajax.php and the plugin's REST routes via a WAF or .htaccess rules scoped to authenticated sessions or known IPs (trade-off: may break legitimate AJAX-driven bookings for end users), and enabling Patchstack or equivalent virtual patching for this specific CVE if available. Monitor WordPress audit logs for unexpected booking or user-data modifications as a detective control.

Affected VersionsENISA

WpTravelly n/a ≤2.1.7

Affected Packages

euvd wptravelly no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WpTravelly is a tour booking manager plugin published by MagePeople Inc. for WordPress, identified by CPE cpe:2.3:a:magepeople_inc.:wptravelly. The underlying weakness is CWE-290 (Authentication Bypass by Spoofing), a class of flaw in which an attacker forges or replays identifying information so the application accepts requests as if they came from a trusted principal. In WordPress plugin ecosystems, this typically arises from missing or improperly implemented capability checks, nonce verification, or trust placed in client-controlled values such as user IDs in POST parameters or cookies. Because WpTravelly handles booking and tour management actions, bypassing authentication exposes administrative or user-context functions to unauthenticated callers.

Know when Wptravelly gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.5 HIGH

Network-reachable WordPress plugin endpoint with no auth or interaction (AV:N/AC:L/PR:N/UI:N); auth bypass enables integrity tampering only (I:H), no disclosure or DoS (C:N/A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

Unauthenticated Bypass Vulnerability in WpTravelly <= 2.1.7 versions.

Executive ViewAI

Why It Matters

The MagePeople WpTravelly WordPress plugin (versions through 2.1.7) contains an authentication bypass vulnerability allowing unauthenticated remote attackers to modify tour booking data and customer records. This directly threatens the integrity of business transactions and customer trust for any organization operating this plugin. Site operators must immediately isolate or disable the affected plugin while awaiting vendor remediation.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable WpTravelly plugin if operationally feasible; implement network-level access restrictions to plugin endpoints; deploy WAF rules targeting authentication bypass patterns in EUVD-2026-36914; enable comprehensive audit logging and real-time alerting on booking modifications; segment affected WordPress instances on restricted networks; monitor booking data for unauthorized modifications.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy