dbcve.org
TourficWordPress extension · Themefic

CVE-2025-24650

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 2.15.4 or later.
See remediation →
97/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 allows Upload a Web Shell to a Web Server.This issue affects Tourfic: from n/a through <= 2.15.3.

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

Unrestricted file upload vulnerability in the Tourfic WordPress plugin allows attackers to upload dangerous file types, specifically web shells, directly to the web server. This enables remote code execution and full server compromise.

MitigationUpdate Tourfic plugin to the latest version immediately. Audit the server for suspicious uploaded files and review access logs for signs of 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
TourficWordPress extension
Affected:< 2.15.4

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Verify Tourfic plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Tourfic' or 'Themefic Tourfic' in the list of active plugins.
    Affected if The Tourfic plugin appears in the installed plugins list.
  2. Check installed Tourfic version
    In WordPress admin, go to Plugins > Installed Plugins, find Tourfic, and note the version number displayed below the plugin name. Alternatively, check the plugin file 'tourfic/tourfic.php' and locate the 'Version' header comment.
    Affected if The installed version is lower than 2.15.4 (for example, 2.15.3, 2.15.2, etc.).
  3. Confirm authenticated user access exists
    Review WordPress user accounts in Users > All Users to determine if there are any user accounts with contributor, author, editor, or administrator roles that could potentially access the plugin's file upload functionality.
    Affected if There is at least one user account with access to the WordPress admin panel or API endpoints used by Tourfic.
  4. Identify if file upload endpoint is accessible
    Check if the Tourfic plugin's upload functionality is enabled by reviewing plugin settings under Tourfic > Settings or checking for frontend forms that accept file uploads (such as tour booking forms). Inspect network requests to identify upload endpoints.
    Affected if File upload forms or API endpoints handled by Tourfic are accessible to authenticated users.

You are affected if the Tourfic plugin is installed with a version lower than 2.15.4 and any authenticated user account exists with access to the plugin's file upload features.

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.15.4 or later
Fixed in 2.15.4
Interim mitigation

Update Tourfic plugin to the latest version immediately. Audit the server for suspicious uploaded files and review access logs for signs of exploitation.

Recommended fix High confidence

Tourfic 2.15.4

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate the Tourfic plugin
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.15.4 or later
  6. 6. Alternatively, download the latest version from the WordPress plugin repository or Themefic's official site
  7. 7. Verify the installed version is 2.15.4 or higher after updating
  8. 8. Test that the file upload functionality works correctly with legitimate file types

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

Fix this in Tourfic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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