Skip to main content
CVE-2024-0434VulnerabilityPublished Updated

CVE-2024-0434: Travelly (WordPress plugin) · Improper Access Control

Affects Travelly (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 May 2024

  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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
magepeopleteam Travelly – Tour & Travel Booking Manager for WooCommerce | Tour & Hotel Booking SolutionAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is available, restrict access to the plugin and monitor for unauthorized content creation. Consider disabling or limiting the use of the affected functionality if possible. Implement web application firewall (WAF) rules to block unauthorized requests targeting the vulnerable function. Avoid clicking on suspicious links that could trigger CSRF attacks.

Description

The WordPress Tour & Travel Booking Plugin for WooCommerce – WpTravelly plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ttbm_new_place_save' function in all versions up to, and including, 1.7.1. This makes it possible for unauthenticated attackers to create and publish new place posts. This function is also vulnerable to CSRF.

References

Community reviews

Loading reviews…