dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32618

HIGH · 8.5 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 PickPlugins Wishlist wishlist allows SQL Injection.This issue affects Wishlist: from n/a through <= 1.0.46.

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

SQL injection vulnerability in PickPlugins Wishlist WordPress plugin (versions <= 1.0.46) allows attackers to inject malicious SQL commands through unsanitized user input in wishlist functionality, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade to patched version of PickPlugins Wishlist plugin when available; until then, implement input sanitization/parameterized queries at application layer or disable the plugin if unpatched.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check PickPlugins Wishlist plugin version
    In WordPress admin, go to Plugins > Installed Plugins > PickPlugins Wishlist and read the Version number. Alternatively, check the main plugin file (e.g., /wp-content/plugins/pickplugins-wishlist/pickplugins-wishlist.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is lower than 1.0.46 (e.g., 1.0.45, 1.0.44, etc.)
  2. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the PickPlugins Wishlist plugin shows as 'Active'.
    Affected if The plugin is active and the version is below 1.0.46
  3. Confirm wishlist functionality is in use
    Check if any Wishlist shortcode (e.g., [wishlist], [pickplugins_wishlist]) is embedded on pages/posts, or if wishlist buttons are displayed on products/posts on the site.
    Affected if Wishlist functionality is actively displayed or used on the site and the plugin version is below 1.0.46

A user is affected if the PickPlugins Wishlist plugin is installed, active, running a version below 1.0.46, and the wishlist feature is enabled on their website.

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

Upgrade to patched version of PickPlugins Wishlist plugin when available; until then, implement input sanitization/parameterized queries at application layer or disable the plugin if unpatched.

Recommended fix Moderate confidence

Latest version of PickPlugins Wishlist (version > 1.0.46)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'PickPlugins Wishlist' plugin
  4. 4. Check the current installed version (should be <= 1.0.46)
  5. 5. Navigate to Plugins > Add New > Upload Plugin or check for an update via Plugins > Installed Plugins
  6. 6. Update to the latest version of the PickPlugins Wishlist plugin
  7. 7. Verify the update was successful and the plugin is functioning normally
Caveat Review plugin settings after upgrade as configuration may need reconfiguration

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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