Quick answers
- Is CVE-2026-62063 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62063 being exploited in the wild.
- How severe is CVE-2026-62063?
- Medium severity, with a CVSS score of 5.4, published 1 October 2026.
- Which products and versions are affected?
- Magepeople inc. WpTravelly tour-booking-manager through 2.3.1.
- Is there a fix for CVE-2026-62063?
- Yes: fixed in 2.3.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62063 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-62063?
- Check whether you run Magepeople inc. WpTravelly tour-booking-manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.3.2
Technical details
The plugin has incorrectly configured access controls that fail to properly validate user permissions before granting access to sensitive pages or functions. A user with contributor-level permissions or above can bypass these controls to access restricted resources. The vulnerability requires authenticated user interaction and affects versions through 2.3.1; a patch is available in version 2.3.2.
Affected products
- Magepeople inc. WpTravelly tour-booking-manager through 2.3.1
Timeline
- 2026-10-01: disclosed: Vulnerability published by Patchstack
- 2026-09-06: other: Reported to Patchstack