dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-60173

HIGH · 7.1 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Ashwani kumar GST for WooCommerce gst-for-woocommerce allows Stored XSS.This issue affects GST for WooCommerce: from n/a through <= 2.0.

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

CSRF vulnerability in the GST for WooCommerce WordPress plugin allows attackers to trick authenticated administrators into executing malicious requests that inject and store XSS payloads. Since the XSS is stored, it persists and executes whenever other admin users view the affected data.

MitigationApply any available vendor patch; until then, implement CSRF tokens on all form submissions and AJAX actions, plus proper input sanitization and output encoding to prevent stored XSS.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Identify GST for WooCommerce plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'GST for WooCommerce' (or 'WooCommerce GST'), and record the version number displayed. Alternatively, check the plugin's main PHP file header for 'Version:' tag, typically in wp-content/plugins/gst-for-woocommerce/gst-woocommerce.php
    Affected if Plugin is installed and version falls within the vulnerable range (compare to official vendor advisory for exact version numbers)
  2. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the GST for WooCommerce plugin shows as 'Active'
    Affected if Plugin is active and vulnerable version is installed
  3. Inspect plugin for CSRF token implementation
    Access plugin source files via FTP or file manager at wp-content/plugins/gst-for-woocommerce/. Examine form handling files (look for PHP files processing adminPOST/GET requests) and check if each form and AJAX action includes wp_nonce_field() or check_admin_referer() calls for nonce verification
    Affected if Forms or AJAX actions lack CSRF token validation (wp_nonce_field/check_admin_referer missing)
  4. Check database for suspicious stored scripts
    Access WordPress database via phpMyAdmin or mysql CLI. Query plugin-related options and postmeta tables: SELECT * FROM wp_options WHERE option_name LIKE '%gst%'; SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%'; Look for any XSS payloads in GST-related settings
    Affected if Any script tags or encoded XSS payloads found in GST plugin configuration data
  5. Review admin pages for injected scripts
    Navigate to all GST for WooCommerce settings pages in the admin dashboard. View page source (right-click > View Page Source) and search for unexpected <script> tags, on* event handlers, or javascript: URIs not originating from the plugin's known files
    Affected if Unexpected JavaScript executes or appears in page source when viewing GST settings pages

User is affected if GST for WooCommerce plugin is installed with a vulnerable version, is active, lacks CSRF protection on its forms/AJAX, AND has stored XSS payloads present in the database or executing on admin pages.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available vendor patch; until then, implement CSRF tokens on all form submissions and AJAX actions, plus proper input sanitization and output encoding to prevent stored XSS.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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