Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-60173: CWE-352 Cross-Site Request Forgery (CSRF) in Ashwani kumar GST for WooCommerce

0
High
VulnerabilityCVE-2025-60173cvecve-2025-60173cwe-352
Published: Fri Sep 26 2025 (09/26/2025, 08:32:09 UTC)
Source: CVE Database V5
Vendor/Project: Ashwani kumar
Product: GST for WooCommerce

Description

Cross-Site Request Forgery (CSRF) vulnerability in Ashwani kumar GST for WooCommerce allows Stored XSS. This issue affects GST for WooCommerce: from n/a through 2.0.

AI-Powered Analysis

AILast updated: 09/27/2025, 00:17:42 UTC

Technical Analysis

CVE-2025-60173 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability identified in the Ashwani kumar GST for WooCommerce plugin, which is used to manage Goods and Services Tax (GST) calculations within WooCommerce-based e-commerce sites. The vulnerability affects versions up to 2.0 of the plugin. The core issue is that the plugin does not adequately verify the authenticity of requests, allowing attackers to craft malicious requests that can be executed by authenticated users without their consent. This CSRF flaw can be leveraged to perform Stored Cross-Site Scripting (XSS) attacks, where malicious scripts are injected and persist within the application, potentially affecting multiple users. The CVSS 3.1 base score of 7.1 reflects a high severity, with the vector indicating that the attack can be performed remotely (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R). The vulnerability impacts confidentiality, integrity, and availability (C:L/I:L/A:L) and has a scope change (S:C), meaning the attack can affect resources beyond the vulnerable component. The absence of patches at the time of publication increases the risk, although no known exploits in the wild have been reported yet. The vulnerability is particularly critical because WooCommerce is widely used for e-commerce, and the GST plugin is integral for tax compliance in regions where GST is applicable. Exploitation could lead to unauthorized actions such as altering tax settings, injecting malicious scripts that steal user data or session tokens, or disrupting the normal operation of the e-commerce platform.

Potential Impact

For European organizations, especially those operating e-commerce platforms using WooCommerce with the Ashwani kumar GST plugin, this vulnerability poses significant risks. Although GST is primarily an Indian tax system, European merchants selling to or through Indian markets or using this plugin for tax calculations might be affected. The Stored XSS component could lead to session hijacking, theft of sensitive customer data, or fraudulent transactions, undermining customer trust and potentially violating GDPR regulations. The CSRF aspect allows attackers to perform unauthorized actions on behalf of authenticated users, which could result in financial discrepancies, manipulation of tax data, or disruption of sales processes. The scope change in the vulnerability means that the impact could extend beyond the plugin itself, potentially affecting other parts of the WooCommerce installation or integrated systems. Given the high reliance on e-commerce in Europe and the strict regulatory environment around data protection and financial transactions, exploitation could lead to legal liabilities, reputational damage, and financial losses.

Mitigation Recommendations

European organizations should immediately assess whether they use the Ashwani kumar GST for WooCommerce plugin and identify the affected versions. Since no patches are currently available, organizations should consider the following specific mitigations: 1) Temporarily disable or remove the GST plugin until a secure update is released. 2) Implement Web Application Firewall (WAF) rules to detect and block CSRF attempts and suspicious POST requests targeting the plugin's endpoints. 3) Enforce strict Content Security Policy (CSP) headers to mitigate the impact of Stored XSS by restricting script execution sources. 4) Educate users and administrators about the risks of unsolicited links or actions that could trigger CSRF attacks. 5) Monitor logs for unusual activities related to tax settings or plugin usage. 6) Plan for immediate patch deployment once the vendor releases a fix. 7) Review and strengthen overall WooCommerce and WordPress security configurations, including ensuring that nonces and anti-CSRF tokens are properly implemented in custom or third-party plugins.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-09-25T15:28:19.138Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d72b6279aa5c9d0854f4c5

Added to database: 9/27/2025, 12:10:10 AM

Last enriched: 9/27/2025, 12:17:42 AM

Last updated: 10/7/2025, 1:52:04 PM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats