Skip to main content
CVE-2026-111213VulnerabilityPublished

The Travelly – Tour & Travel Booking Manager for WooCommerce plugin for WordPress is vulnerable to authorization

Source GCVE Database

0
Authoritative record:CVE-2026-111213· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 28 Oct 2026, 10:27 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
magepeopleteamTravelly – Tour & Travel Booking Manager for WooCommerceAffected
  • <=2.3.6
Fixed in–

AI-suggested

Until a fix is available, restrict contributor-level access to trusted users only and monitor for updates from the plugin vendor. Avoid using the affected versions if possible.

Description

The Travelly – Tour & Travel Booking Manager for WooCommerce plugin for WordPress versions up to 2.3.6 contains an authorization bypass vulnerability. Authenticated users with contributor-level access or higher can exploit this flaw to duplicate arbitrary posts, including private, draft, and pending posts authored by higher-privileged users. This duplication exposes sensitive content such as the original post's content, excerpt, title, taxonomies, and metadata. The vulnerability arises because the plugin does not properly verify user authorization and uses a static nonce action that is not bound to specific posts, allowing nonce reuse against any post ID.

References

Community reviews

Loading reviews…