dbcve.org
TourficWordPress extension · Themefic

CVE-2024-29136

HIGH · 8.8 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 2.11.19 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
Deserialization of Untrusted Data vulnerability in Themefic Tourfic tourfic.This issue affects Tourfic: from n/a through <= 2.11.17.

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 a PHP object injection/deserialization vulnerability in the Tourfic WordPress plugin. The vulnerability allows unauthenticated attackers to inject malicious PHP objects by tricking the application into deserializing untrusted data, potentially leading to remote code execution if a suitable gadget chain exists within the WordPress environment or loaded libraries.

MitigationUpdate Tourfic plugin to the latest version immediately. If unable to update, restrict access to affected endpoints and review server-side deserialization handling for proper input validation and sanitization.

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.19

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. Verify Tourfic plugin is installed
    Check the WordPress plugins directory for the tourfic folder: ls -la /path/to/wordpress/wp-content/plugins/ | grep tourfic, or view Plugins page in WordPress admin
    Affected if Tourfic plugin is found in the WordPress installation
  2. Determine installed Tourfic version
    Open the main plugin file (tourfic/tourfic.php) and check the Version header in the plugin comment block, or use WP-CLI: wp plugin get tourfic --field=version
    Affected if Version number is less than 2.11.19
  3. Identify vulnerable deserialization code
    Search the tourfic plugin directory for unserialize() calls: grep -r "unserialize" /path/to/wordpress/wp-content/plugins/tourfic/ --include="*.php"
    Affected if Code contains unserialize() calls handling untrusted input without prior validation
  4. Verify endpoint accessibility
    Review the identified unserialize() calls in context - check if they are reachable via public AJAX actions or front-end requests without authentication
    Affected if The deserialization function is accessible without authentication and processes user-supplied data

You are affected if Tourfic plugin version is below 2.11.19 AND the plugin contains unserialize() calls processing untrusted input that are accessible to unauthenticated users.

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.19 or later
Fixed in 2.11.19
Interim mitigation

Update Tourfic plugin to the latest version immediately. If unable to update, restrict access to affected endpoints and review server-side deserialization handling for proper input validation and sanitization.

Recommended fix High confidence

2.11.19

  1. Backup your WordPress site and database before making any changes
  2. Update the Tourfic plugin to version 2.11.19 or later through the WordPress admin dashboard (Plugins > Add New > Upload, or update via the Plugins page)
  3. Verify the update was successful by checking the installed version number
  4. Clear any caching mechanisms if your site uses them

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

Fix this in Tourfic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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