dbcve.org
TourficWordPress extension · Themefic

CVE-2024-29135

HIGH · 8.8 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 2.11.16 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
Unrestricted Upload of File with Dangerous Type vulnerability in Themefic Tourfic tourfic.This issue affects Tourfic: from n/a through <= 2.11.15.

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 · moderate confidence

This is an unrestricted file upload vulnerability in the Tourfic WordPress plugin. The plugin fails to properly validate file types during upload operations, allowing attackers to upload dangerous file types (such as executable PHP scripts) that could lead to remote code execution and complete site compromise.

MitigationUpdate Tourfic plugin to the latest version above 2.11.15 which contains proper file type validation. If immediate updating is not possible, disable file upload functionality or deploy WAF rules to block executable file uploads.

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
TourficWordPress extension
Affected:< 2.11.16

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. Check Tourfic plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > Look for 'Themefic Tourfic' and note the version number displayed
    Affected if Installed version is lower than 2.11.16
  2. Identify if Tourfic upload feature is in use
    Check if the plugin's file upload functionality is enabled. This may be configured in Tourfic settings under Hotel, Tour, or Apartment booking settings where file/document uploads are permitted
    Affected if File upload feature is enabled in Tourfic settings and plugin version is below 2.11.16
  3. Inspect upload directory for suspicious files
    Navigate to wp-content/uploads/tourfic/ directory via FTP or file manager. Look for files with extensions such as .php, .phtml, .phar, .php5, .php7, .js, .exe, .sh, or other executable extensions
    Affected if Any PHP files or other executable scripts are found in upload directories and plugin version is below 2.11.16
  4. Review access logs for upload endpoint activity
    Examine web server access logs (Apache/Nginx) for POST requests to Tourfic upload endpoints. Look for patterns like /wp-json/tourfic/v1/upload/ or similar upload-related paths with unusual file types
    Affected if Logs show uploads of file types other than standard images (jpg, png, pdf) and plugin version is below 2.11.16

You are affected if the Tourfic plugin version is below 2.11.16 AND the file upload functionality is enabled or was recently active on the site.

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 2.11.16 or later
Fixed in 2.11.16
Interim mitigation

Update Tourfic plugin to the latest version above 2.11.15 which contains proper file type validation. If immediate updating is not possible, disable file upload functionality or deploy WAF rules to block executable file uploads.

Recommended fix High confidence

2.11.16

  1. Backup your WordPress site and database before updating any plugin
  2. Navigate to your WordPress admin dashboard > Plugins
  3. Locate the Tourfic plugin in the installed plugins list
  4. Check the current version - if it shows 2.11.15 or below, it is vulnerable
  5. Click 'Update now' when an update to version 2.11.16 is available
  6. Alternatively, download Tourfic version 2.11.16 from the WordPress plugin repository
  7. If automatic update does not work, deactivate and delete the old plugin, then upload and install version 2.11.16
  8. After updating, verify the plugin is now running version 2.11.16 in the plugins list

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

Fix this in Tourfic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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