dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-32418

HIGH · 7.6 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Jordy Meow Meow Gallery meow-gallery allows Blind SQL Injection.This issue affects Meow Gallery: from n/a through <= 5.4.4.

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 · high confidence

A blind SQL injection vulnerability exists in the Meow Gallery WordPress plugin (versions up to 5.4.4). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through improper neutralization of special elements in SQL commands. Unlike standard SQL injection, blind SQLi requires attackers to infer information by observing behavioral differences (e.g., response variations or time delays) rather than viewing direct database output.

MitigationUpgrade to a patched version of Meow Gallery that properly sanitizes and parameterizes all user-supplied input in SQL queries. If no patch is available, disable 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
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 checks

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

  1. Verify Meow Gallery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Meow Gallery' in the list. Alternatively, check for the plugin directory at /wp-content/plugins/meow-gallery/
    Affected if The Meow Gallery plugin appears in the list of installed plugins and is activated
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Meow Gallery and note the version number displayed below the plugin name. Or read the 'readme.txt' or 'meow-gallery.php' file header in the plugin directory
    Affected if The installed version is 5.4.4 or any earlier version (versions 'up to 5.4.4' are affected)
  3. Confirm the plugin is publicly accessible
    Attempt to access the frontend of the WordPress site where Meow Gallery is used, or check if AJAX endpoints under /wp-admin/admin-ajax.php or /wp-json/ are reachable without authentication
    Affected if The plugin endpoints are reachable without authentication (the vulnerability is unauthenticated)
  4. Identify potential injection points
    Review HTTP requests to the site for parameters passed to Meow Gallery functionality (common paths: /?meow_gallery_action=..., /?ml_gallery=..., or AJAX calls). Use browser developer tools or a proxy to inspect request parameters when the gallery loads
    Affected if User-controllable parameters are being passed to the plugin without visible sanitization in the HTTP requests

You are affected if Meow Gallery plugin is installed with version 5.4.4 or earlier and is accessible to unauthenticated users, as the blind SQL injection can be triggered through plugin parameters.

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

Upgrade to a patched version of Meow Gallery that properly sanitizes and parameterizes all user-supplied input in SQL queries. If no patch is available, disable the plugin until a fix is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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