CVE-2025-32687
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 Magnigenie Review Stars Count For WooCommerce review-stars-count-for-woocommerce allows SQL Injection.This issue affects Review Stars Count 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 confidenceSQL Injection vulnerability in the Review Stars Count For WooCommerce plugin allows attackers to inject malicious SQL commands through unsanitized input in review-related functionality. The vulnerability affects all versions through 2.0 and can be exploited to read, modify, or delete database content.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 Review Stars Count For WooCommerce pluginCheck your WordPress installation's wp-content/plugins directory for a folder named 'review-stars-count-for-woocommerce' or similar variant. In WordPress admin, go to Plugins > Installed Plugins and look for this plugin.Affected if The plugin folder or entry exists in the plugins directory
-
Identify the installed versionIn WordPress admin, find the plugin in Plugins > Installed Plugins and note the version number displayed. Alternatively, check the main plugin PHP file (usually review-stars-count-for-woocommerce.php) for a 'Version:' header in the plugin comment block.Affected if The version is 2.0 or lower (the vulnerability affects all versions through 2.0)
-
Verify review functionality is activeCheck if WooCommerce is installed and the Review Stars Count plugin settings are enabled. Look for any review star display features or review count functionality that may be rendering on the site.Affected if WooCommerce reviews are enabled and the plugin is actively displaying review stars or counts on product pages
-
Inspect the vulnerable review-related codeExamine the main plugin PHP file for SQL queries that handle review data. Look for direct database queries using $wpdb->prepare or similar functions where review IDs, product IDs, or user input flows into the query without proper sanitization. Search for terms like 'get_comments', 'review', 'star', 'rating' in the code.Affected if SQL queries in the plugin code accept user-supplied review parameters without using parameterized queries or proper escaping
You are affected if the Review Stars Count For WooCommerce plugin is installed with version 2.0 or lower and review-related features are active on the site.
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 the Review Stars Count For WooCommerce plugin to the latest version once available, or implement input sanitization/parameterized queries in the plugin code to neutralize SQL special characters before database queries.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32687 — 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-32687 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