CVE-2026-111213
Received Received - Intake

Authorization Bypass in Travelly WooCommerce Plugin

Vulnerability report for CVE-2026-111213, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-28

Last updated on: 2026-10-28

Assigner: Wordfence

Description

The Travelly – Tour & Travel Booking Manager for WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.3.6 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to duplicate arbitrary posts β€” including private, draft, and pending posts authored by Administrators and Editors β€” into drafts they own, thereby exposing the original post's content, excerpt, title, taxonomies, and metadata. A Contributor can harvest a valid nonce from the Duplicate row-action on their own posts list and reuse it against any victim post ID, since the nonce action is the static string 'TTBM_Admin.php' and is not bound to any specific post.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-28
Last Modified
2026-10-28
Generated
2026-10-28
AI Q&A
2026-10-28
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Travelly plugin for WordPress has an authorization bypass flaw in versions up to 2.3.6. Authenticated attackers with contributor-level access or higher can duplicate posts, including private or draft posts by admins, exposing their content and metadata. The flaw exists because the plugin uses a static nonce string not tied to specific posts.

Detection Guidance

Check WordPress installations for the Travelly plugin versions up to 2.3.6. Look for unauthorized post duplications or unusual activity in post logs. Review user roles with contributor access or higher for suspicious actions.

Impact Analysis

Attackers could steal sensitive content from private or draft posts, including those by admins. This could lead to data leaks, unauthorized access to unpublished content, or misuse of exposed metadata. The impact is limited to authenticated users with contributor access or higher.

Compliance Impact

This vulnerability could lead to unauthorized exposure of sensitive data, potentially violating GDPR (data protection) or HIPAA (health information privacy) if such data is leaked. Organizations using this plugin may face compliance risks due to potential data breaches.

Mitigation Strategies

Update the Travelly plugin to the latest version beyond 2.3.6. Remove contributor-level access for users unless absolutely necessary. Monitor post duplication events and restrict post editing permissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111213. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart