CVE-2026-66652 in Grand Tour Plugininfo

Summary

by MITRE • 09/02/2026

Cross-Site Request Forgery (CSRF) vulnerability in ThemeGoods Grand Tour allows Cross Site Request Forgery.

This issue affects Grand Tour: from n/a through 5.5.1.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 09/02/2026

The identified security flaw represents a classic Cross-Site Request Forgery, or CSRF, vulnerability within the Grand Tour theme developed by ThemeGoods. This type of attack exploits the trust that a web application has in the user's browser to execute unintended actions on behalf of an authenticated user without their knowledge or consent. The vulnerability exists because the affected software versions fail to implement adequate mechanisms to verify that incoming requests originate from legitimate, expected sources rather than malicious third-party sites. By leveraging this weakness, an attacker can craft a deceptive webpage containing hidden forms or automated scripts that trigger state-changing operations within the Grand Tour application while the victim is logged in and their session remains active.

The technical root cause lies in the absence of robust anti-CSRF tokens or insufficient validation of the Origin and Referer headers during sensitive transactions. In many web applications, especially those built on frameworks like WordPress which often utilize themes such as Grand Tour, actions that modify data must include a unique, unpredictable token tied to the user's session. Without this cryptographic challenge-response mechanism, any request sent by the browser is processed if it contains valid authentication cookies. Consequently, an attacker can trick a victim into clicking a link or visiting a malicious site that silently submits requests to change account settings, update profile information, or perform financial transactions within the Grand Tour environment.

The operational impact of this vulnerability extends beyond simple data modification. If the vulnerable endpoints allow for administrative actions or user role changes, the consequences can be severe, including complete compromise of the website's integrity and availability. Attackers may use CSRF to deface websites, steal sensitive information stored in session variables, or escalate privileges by changing administrator passwords. For e-commerce functionalities often integrated into such themes, this could lead to unauthorized purchases, coupon code manipulation, or payment method alterations. The lack of proper request validation means that the application cannot distinguish between a legitimate user action and a forged one, thereby undermining the fundamental principle of state integrity in web interactions.

This vulnerability aligns with CWE-352, which defines Cross-Site Request Forgery as a weakness where an attacker causes a user to submit a request to a vulnerable web application without their consent. From a tactical perspective, this falls under MITRE ATT&CK technique T1078, specifically related to valid accounts and potentially T1190 for exploiting public-facing applications. The exploitation typically involves social engineering components where the victim is lured into triggering the malicious request through phishing emails or compromised websites that host the exploit payload.

To mitigate this risk, developers must implement anti-CSRF tokens in all forms and AJAX requests that modify state. These tokens should be unique per session and validated server-side before processing any action. Additionally, enforcing strict checks on HTTP Origin and Referer headers can provide an additional layer of defense by ensuring requests originate from the expected domain. Setting cookies with the SameSite attribute to Strict or Lax further prevents browsers from sending these credentials in cross-site contexts. For users running Grand Tour versions up through 5.5.1, upgrading to a patched version that includes these security controls is essential to restore trust and prevent unauthorized actions initiated by malicious actors exploiting this flaw.

Responsible

Patchstack

Reservation

07/27/2026

Disclosure

09/02/2026

Moderation

accepted

CPE

ready

EPSS

0.00095

KEV

no

Activities

low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!