CVE-2026-32486
Missing Authorization in wptravelengine Travel Booking Plugin
Publication date: 2026-03-13
Last updated on: 2026-03-13
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wptravelengine | travel_booking | to 1.3.9 (inc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-32486 is a broken access control vulnerability in the WordPress Travel Booking Theme versions up to and including 1.3.9.
The issue arises from missing authorization, authentication, or nonce token checks within certain functions, which allows unauthenticated users to perform actions that normally require higher privileges.
This vulnerability falls under the OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability impact me? :
Because the vulnerability allows unauthenticated users to perform privileged actions, it can lead to unauthorized changes or actions within the Travel Booking system.
However, the CVSS severity score is 5.3, indicating a low severity impact, and it is considered unlikely to be exploited in a significant manner.
Users are advised to update to version 1.4.0 or later to mitigate this risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization checks in the WordPress Travel Booking Theme up to version 1.3.9, allowing unauthenticated users to perform privileged actions.
Detection would involve checking for unauthorized access attempts or actions that should require higher privileges but are accessible without authentication.
Since the vulnerability is related to broken access control in specific theme functions, detection might include reviewing web server logs for suspicious requests targeting the Travel Booking theme endpoints.
No specific commands or automated detection scripts are provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the WordPress Travel Booking Theme to version 1.4.0 or later, where the vulnerability has been patched.
Since the vulnerability allows unauthenticated users to perform privileged actions, applying the update promptly is critical to prevent exploitation.
No additional mitigation steps such as configuration changes or workarounds are mentioned in the provided resources.