dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-54849

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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
Unauthenticated SQL Injection in Premmerce Wishlist for WooCommerce <= 1.1.11 versions.

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

Unauthenticated SQL Injection vulnerability in Premmerce Wishlist for WooCommerce plugin affecting versions 1.1.11 and below. Attackers can inject malicious SQL queries without any authentication, potentially allowing database exfiltration, manipulation, or complete system compromise.

MitigationUpdate Premmerce Wishlist for WooCommerce to a version newer than 1.1.11 immediately. If no patched version is available, consider removing the plugin until a fix is released.

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 checks

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

  1. Verify Premmerce Wishlist for WooCommerce is installed
    Access WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Premmerce Wishlist for WooCommerce' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the plugins list, locate the Premmerce Wishlist for WooCommerce entry and note the version number displayed beneath the plugin name. Alternatively, inspect the main plugin file (usually premmerce-wishlist.php or similar) in wp-content/plugins/ and look for the 'Version' header in the plugin comment block.
    Affected if The displayed version is 1.1.11 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that the Premmerce Wishlist for WooCommerce plugin has the 'Active' status indicator (not deactivated or inactive).
    Affected if The plugin is active and the version is 1.1.11 or below
  4. Verify the wishlist functionality is publicly accessible
    Visit the site frontend and confirm the wishlist feature is visible and functional (e.g., wishlist button, wishlist page). Since this is an unauthenticated SQLi, the vulnerable code executes even without authentication.
    Affected if The wishlist feature is publicly accessible and the plugin version is 1.1.11 or below

If Premmerce Wishlist for WooCommerce is installed, active, at version 1.1.11 or below, and the wishlist feature is accessible on the frontend, the environment is affected by this unauthenticated 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Premmerce Wishlist for WooCommerce to a version newer than 1.1.11 immediately. If no patched version is available, consider removing the plugin until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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