dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-0434

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WpTravelly WordPress plugin versions up to 1.7.1 contain a broken access control vulnerability in the ttbm_new_place_save function. This function lacks proper capability checks, allowing unauthenticated attackers to create and publish arbitrary place posts. The function is also vulnerable to cross-site request forgery (CSRF), enabling attackers to trick authenticated users into executing the malicious request.

MitigationUpdate the WpTravelly plugin to version 1.7.2 or later, which includes the missing capability check. Verify that unauthenticated users can no longer create or publish place posts after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WpTravelly plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and locate WpTravelly plugin. Note the version number displayed.
    Affected if WpTravelly plugin is installed with version 1.7.1 or earlier
  2. Confirm plugin version range
    Compare the installed version against the affected range (versions up to and including 1.7.1). The fixed version is 1.7.2.
    Affected if Installed version is 1.7.1 or earlier, meaning the capability check patch has not been applied
  3. Inspect ttbm_new_place_save function accessibility
    Check the plugin PHP files for the ttbm_new_place_save function and verify if it is hooked to wp_ajax or wp_ajax_nopriv hooks. Look for add_action('wp_ajax_nopriv_ttbm_new_place_save', ...) which would expose it to unauthenticated users.
    Affected if The function is hooked to wp_ajax_nopriv_ or has no capability check, allowing unauthenticated access
  4. Test for CSRF protection
    Review the ttbm_new_place_save function code to verify if it implements nonce verification or other CSRF protection mechanisms before processing requests.
    Affected if No nonce verification or CSRF token validation is present in the function
  5. Verify capability check exists
    Examine the ttbm_new_place_save function to determine if it calls current_user_can() or similar WordPress capability checks before allowing post creation and publication.
    Affected if No capability check (such as current_user_can('publish_posts')) is performed before creating and publishing place posts

If WpTravelly plugin version is 1.7.1 or earlier and the ttbm_new_place_save function lacks capability checks and is accessible to unauthenticated users, the environment is affected by CVE-2024-0434.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WpTravelly plugin to version 1.7.2 or later, which includes the missing capability check. Verify that unauthenticated users can no longer create or publish place posts after the update.

Recommended fix Moderate confidence

Version 1.7.2 or latest available version (after 1.7.1)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the 'Tour & Travel Booking Plugin for WooCommerce – WpTravelly' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify that the plugin functions correctly with your WooCommerce installation
Caveat Minor: Review plugin settings after upgrade to ensure configuration is intact

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0434 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0434 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data