dbcve.org
Tour MasterWordPress extension · Goodlayers

CVE-2024-13369

HIGH · 8.8 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 5.3.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Tour Master - Tour Booking, Travel, Hotel plugin for WordPress is vulnerable to time-based SQL Injection via the ‘review_id’ parameter in all versions up to, and including, 5.3.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Tour Master WordPress plugin (versions up to 5.3.7) contains a time-based SQL injection vulnerability in the 'review_id' parameter. The flaw stems from insufficient input sanitization and lack of prepared statements in the SQL query handling, allowing authenticated attackers with Subscriber-level access or higher to inject arbitrary SQL commands. As a time-based (blind) SQLi, attackers infer database information through conditional time delays.

MitigationUpgrade to version 5.3.8 or later, which implements proper SQL escaping and prepared statements for the review_id parameter. Until patched, disable the plugin or restrict user registration to prevent exploitation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tour MasterWordPress extension
Affected:< 5.3.8

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Tour Master plugin is installed
    Check WordPress plugins directory or wp-admin plugins list for 'Tour Master' or 'Goodlayers Tour Master'
    Affected if Tour Master plugin is found installed on the WordPress site
  2. Identify the installed plugin version
    View plugin details in WordPress admin under Plugins > Installed Plugins, or inspect the plugin main file header for version number
    Affected if Installed version is less than 5.3.8 (versions 5.3.7 and below are affected)
  3. Verify subscriber-level user accounts exist
    Check WordPress user roles under Users menu for any accounts with Subscriber role
    Affected if At least one user with Subscriber role exists on the site
  4. Confirm review functionality is accessible
    Inspect if the review submission or viewing feature using the 'review_id' parameter is accessible on the frontend
    Affected if The review feature that accepts review_id parameter is active and accessible to authenticated users

The site is affected if Tour Master plugin version is below 5.3.8, the site has subscriber-level users, and the review functionality using review_id is accessible.

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
Upgrade available Upgrade to 5.3.8 or later
Fixed in 5.3.8
Interim mitigation

Upgrade to version 5.3.8 or later, which implements proper SQL escaping and prepared statements for the review_id parameter. Until patched, disable the plugin or restrict user registration to prevent exploitation.

Recommended fix High confidence

Tour Master version 5.3.8

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the Tour Master plugin in the list.
  4. 4. If an update is available, click the 'Update Now' link next to the plugin, or go to Dashboard > Updates and select Tour Master to update.
  5. 5. Alternatively, download version 5.3.8 from the source (codecanyon.net) and upload/install it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin status shows version 5.3.8.

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

Fix this in Tour Master Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13369 — 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-13369 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