dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30765

HIGH · 7.6 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPPOOL FlexStock stock-sync-with-google-sheet-for-woocommerce allows Blind SQL Injection.This issue affects FlexStock: from n/a through <= 3.13.1.

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 · high confidence

A blind SQL injection vulnerability exists in the FlexStock WooCommerce plugin where unsanitized user input is directly incorporated into SQL queries. Attackers can exploit this to extract sensitive data from the database through boolean-based or time-based blind SQL injection techniques.

MitigationUpdate FlexStock to version 3.13.2 or later which should contain the patch. If no patched version is available, disable the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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. Locate FlexStock plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) or use WP-CLI: wp plugin list --name=flexstock --format=table
    Affected if FlexStock plugin directory exists in the installation
  2. Identify installed FlexStock version
    Check the plugin main file header (e.g., flexstock.php) for the Version constant, or run: wp plugin get flexstock --field=version
    Affected if Version is present and below 3.13.2 (e.g., 3.13.1, 3.12.x, etc.)
  3. Confirm plugin is active
    Run: wp plugin is-active flexstock, or check WordPress admin Plugins page for FlexStock status
    Affected if Plugin is active and enabled on the WooCommerce site
  4. Verify vulnerable code path exists
    Examine plugin source files (especially files handling product/stock queries) for direct SQL query construction with unsanitized input from $_GET, $_POST, or $_REQUEST parameters
    Affected if Code contains SQL queries concatenating user input without prepare() or escaping functions
  5. Test for blind SQL injection behavior
    If safe to do in a non-production environment, observe database query behavior when passing special characters (e.g., apostrophe) in plugin-related URL parameters (e.g., ?search=term' OR '1'='1)
    Affected if Application exhibits delayed response (time-based) or different output (boolean-based) when injecting SQL syntax

User is affected if FlexStock plugin is installed, active, and running a version earlier than 3.13.2 with unsanitized user input reaching SQL queries.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update FlexStock to version 3.13.2 or later which should contain the patch. If no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Latest available version of FlexStock from WordPress plugin repository (version > 3.13.1)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the FlexStock (stock-sync-with-google-sheet-for-woocommerce) plugin
  4. Check if the current version is 3.13.1 or earlier
  5. If vulnerable, click 'Update Now' to install the latest available version from the WordPress plugin repository
  6. After updating, verify the new version number in the plugins list
  7. Test the plugin functionality to ensure the stock sync with Google Sheets continues to work correctly
  8. Consider enabling automatic updates for this plugin to receive future security patches promptly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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