CVE-2025-30879
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 Moreconvert Team MC Woocommerce Wishlist smart-wishlist-for-more-convert allows SQL Injection.This issue affects MC Woocommerce Wishlist: from n/a through <= 1.8.9.
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 MC Woocommerce Wishlist plugin allows attackers to inject malicious SQL queries through unsanitized user input in the wishlist functionality. This could enable unauthorized data access, modification, or potentially remote code execution depending on database privileges.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify MC Woocommerce Wishlist plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder containing 'mc-woocommerce-wishlist' or similar wishlist-related plugin files.Affected if The plugin is present in the plugins directory regardless of activation status.
-
Identify installed plugin versionOpen the main plugin file (typically index.php or main .php file in the plugin folder) and locate the version comment or header, or check the plugin details displayed in the WordPress Plugins admin page.Affected if The installed version is lower than 1.8.9 (e.g., 1.8.8, 1.8.7, earlier versions).
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the MC Woocommerce Wishlist plugin status shows as 'Active', or query the wp_options table for the active_plugins option.Affected if The plugin is activated on the site.
-
Verify wishlist functionality is publicly accessibleVisit the site frontend and attempt to access a wishlist page or feature (common paths: /wishlist, /my-wishlist, or a wishlist button on product pages). Check if non-authenticated users can interact with wishlist features.Affected if Wishlist pages or endpoints are accessible to unauthenticated visitors.
-
Inspect HTTP requests for unsanitized parametersUse browser developer tools or a proxy to capture a wishlist-related HTTP request (add to wishlist, view wishlist). Examine the request parameters for user-supplied input being passed directly without apparent sanitization.Affected if Wishlist requests contain user input (product IDs, user identifiers, custom notes) sent as plain parameters without visible encoding or prepared statement usage.
The environment is affected if MC Woocommerce Wishlist plugin versions prior to 1.8.9 are installed and active, with wishlist functionality exposed to users.
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 MC Woocommerce Wishlist to the latest version beyond 1.8.9, or apply the vendor's security patch to implement proper input sanitization and parameterized queries.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-30879 — 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-30879 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