CVE-2026-39565
Missing Authorization in WpTravelly Tour-Booking Manager
Publication date: 2026-04-08
Last updated on: 2026-04-29
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| magepeopleteam | wptravelly | to 2.1.7 (inc) |
| magepeople | wptravelly | From 1.0.0 (inc) to 2.1.7 (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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the Broken Access Control vulnerability in the WpTravelly plugin directly affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2026-39565 is a Broken Access Control vulnerability in the WordPress WpTravelly plugin versions up to and including 2.1.7.
The issue arises from missing authorization, authentication, or nonce token checks within certain plugin functions, which allows unprivileged users (such as subscribers or developers) to perform actions that should be restricted to higher-privileged roles.
This vulnerability falls under the OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability impact me? :
This vulnerability allows unprivileged users to perform actions reserved for higher-privileged roles, potentially leading to unauthorized changes or access within the WpTravelly plugin.
Although the CVSS severity score is 4.3, indicating low severity and low priority for exploitation, it can still be leveraged in mass-exploit campaigns targeting many websites indiscriminately.
Users are strongly advised to update to version 2.1.8 or later of the plugin to mitigate this risk.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in the WpTravelly plugin versions up to 2.1.7 can be mitigated by updating the plugin to version 2.1.8 or later, where the issue has been patched.
Users are strongly advised to apply this update promptly to prevent exploitation of the broken access control vulnerability.
Additionally, using mitigation solutions such as auto-updates for vulnerable plugins can provide rapid protection.