CVE-2024-32450

WpTravelly <= 1.6.0 - Cross-Site Request Forgery

2024-04-12 00:00
Dhabaleshwar Das

Strategic Overview

Status
Patched in 1.6.1
Affected Plugin
Travelly – Tour & Travel Booking Manager for WooCommerce
Affected Version
<= 1.6.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-32450
View all Travelly – Tour & Travel Booking Manager for WooCommerce vulnerabilities

At a glance

CVE-2024-32450 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Travelly WordPress plugin, affecting versions <= 1.6.0. 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 1.6.1; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

The WpTravelly plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.6.0. This is due to missing or incorrect nonce validation on the quick_setup() function. This makes it possible for unauthenticated attackers to trigger a set-up 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)

Travelly <= 1.6.0 carries this weakness at quick_setup(), and reaching it 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 Travelly the fix is 1.6.1: builds <= 1.6.0 are affected, anything from 1.6.1 onward is not.

Remediation

Update to version 1.6.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Travelly: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Travelly 1.6.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-32450https://www.wordfence.com/threat-intel/vulnerabilities/id/3e34e774-30fe-49dc-b1f8-8dd63da65d23https://nvd.nist.gov/vuln/detail/CVE-2024-32450

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C