CVE-2025-23967
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in wpopal GG Bought Together for WooCommerce gg-bought-together allows SQL Injection.This issue affects GG Bought Together for WooCommerce: from n/a through <= 1.0.2.
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 confidenceSQL injection vulnerability in the GG Bought Together for WooCommerce plugin allows attackers to inject malicious SQL commands via unsanitized user input in database queries, potentially enabling unauthorized data access or modification of the WooCommerce database.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the GG Bought Together plugin filesCheck your WordPress wp-content/plugins directory for a folder named 'gg-bought-together' or 'gg-bought-together-for-woocommerce'. You can also view the installed plugins list in the WordPress admin under Plugins > Installed Plugins.Affected if The plugin folder is not found in the plugins directory.
-
Identify the installed plugin versionIf the plugin is present, open the main plugin file (usually gg-bought-together.php or index.php) and locate the 'Version' header in the plugin comment block at the top of the file. Alternatively, view the version in the WordPress admin plugins list.Affected if The version displayed cannot be confirmed as patched by the vendor, or no version information is found in the plugin header.
-
Confirm the plugin is active on the siteIn the WordPress admin, go to Plugins > Installed Plugins and check if GG Bought Together is activated. You can also query the wp_options table in the database for the option_name 'active_plugins' and check if gg-bought-together is listed.Affected if The plugin appears in the active_plugins list in the database or shows as 'Active' in the admin interface.
-
Verify the Bought Together feature is in useCheck if the plugin's functionality is enabled on WooCommerce product pages or cart. Look for any frontend output showing 'Bought Together' recommendations, or check the plugin settings in WooCommerce > Settings for any gg-bought-together configuration.Affected if The plugin settings are configured and the feature is actively displaying product recommendations on the storefront.
Your site is affected if the GG Bought Together plugin is installed, active, and running a version that has not been patched by the vendor to address the SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the plugin which should contain patched code with proper input validation and parameterized queries. If no patch is available, disable the plugin until a secure version is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23967 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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