dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-26915

HIGH · 8.5 CVSS v3.1 Published 2025-02-25
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.41.

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 plugin allows attackers to inject malicious SQL commands through unsanitized user input in wishlist functionality. This could enable unauthorized database access, data exfiltration, or modification.

MitigationUpgrade to latest version of PickPlugins Wishlist plugin and implement parameterized queries/prepared statements for all database operations handling user-supplied input.

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. Confirm PickPlugins Wishlist plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PickPlugins Wishlist' in the list
    Affected if Plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Click 'View Details' on the PickPlugins Wishlist plugin in the WordPress plugins page to see the current version number
    Affected if Version is unknown or cannot be compared to a fixed release (no patched version listed in CVE)
  3. Locate wishlist-related PHP files handling user input
    In the plugin directory (wp-content/plugins/pickplugins-wishlist/), search for files containing wishlist functionality and user input handling (look for $_GET, $_POST, $_REQUEST parameters)
    Affected if Plugin processes user input without sanitization in wishlist-related code
  4. Inspect SQL queries in wishlist functionality
    Search plugin PHP files for direct SQL queries (SELECT, INSERT, UPDATE, DELETE) that incorporate user input variables without using $wpdb->prepare() or parameterized queries
    Affected if SQL queries concatenate or interpolate user input directly without preparation
  5. Test wishlist endpoints for SQL injection susceptibility
    If you have access to the source, trace how wishlist parameters (e.g., wishlist ID, user ID, product ID) flow from HTTP requests to database queries; verify if any are used in raw SQL
    Affected if User-controlled parameters from wishlist requests reach SQL statements without sanitization

If the PickPlugins Wishlist plugin is installed and processes user input in wishlist functionality without using prepared statements or input sanitization, the environment is likely affected by this SQL injection vulnerability.

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 latest version of PickPlugins Wishlist plugin and implement parameterized queries/prepared statements for all database operations handling user-supplied input.

Recommended fix Moderate confidence

Version 1.0.42 or later (any version higher than 1.0.41)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'PickPlugins Wishlist' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update completed successfully
  6. 6. Test the wishlist functionality to ensure the plugin is working correctly after the update

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-26915 — 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-26915 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