Tourfic <= 2.11.20 - Cross-Site Request Forgery in Multiple Functions
Strategic Overview
- Status
- Patched in 2.11.21
- Affected Version
<= 2.11.20- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-8319
At a glance
CVE-2024-8319 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Tourfic WordPress plugin, affecting versions <= 2.11.20. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.11.21; sites on affected versions should update now. Disclosed August 2024.
Vulnerability Overview
The Tourfic plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.11.20. This is due to missing or incorrect nonce validation on the tf_order_status_email_resend_function, tf_visitor_details_edit_function, tf_checkinout_details_edit_function, tf_order_status_edit_function, tf_order_bulk_action_edit_function, tf_remove_room_order_ids, and tf_delete_old_review_fields functions. This makes it possible for unauthenticated attackers to resend order status emails, update visitor/order details, edit check-in/out details, edit order status, perform bulk order status updates, remove room order IDs, and delete old review fields, respectively, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Tourfic <= 2.11.20 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Tourfic the fix is 2.11.21: builds <= 2.11.20 are affected, anything from 2.11.21 onward is not.
Remediation
Update to version 2.11.21, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Tourfic: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Tourfic 2.11.21 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Tourfic – AI Powered Travel Booking, Hotel Booking & Car Rental WordPress Plugin
- 8.8CVE-2024-29136: Tourfic <= 2.11.17 PHP Object Injection
CVE-2024-29136 - 8.8CVE-2024-29135: Tourfic <= 2.11.15 Arbitrary File Upload
CVE-2024-29135 - 7.5CVE-2026-12937: Tourfic <= 2.22.7 SQL Injection
CVE-2026-12937 - 7.2CVE-2025-24650: Tourfic <= 2.15.3 Arbitrary File Upload
CVE-2025-24650 - 6.5CVE-2026-56064: Tourfic SQL Injection
CVE-2026-56064 - 6.5CVE-2024-12032: Tourfic SQL Injection
CVE-2024-12032 - 6.4CVE-2024-29134: Tourfic <= 2.11.8 Stored Cross-Site Scripting
CVE-2024-29134 - 6.1CVE-2024-29137: Tourfic <= 2.11.7 Reflected Cross-Site Scripting
CVE-2024-29137
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C