dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39574

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-16
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

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 InPost Gallery <= 2.1.4.6 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 InPost Gallery plugin versions 2.1.4.6 and below allows remote attackers to inject arbitrary SQL commands without any authentication, potentially leading to complete database compromise.

MitigationUpdate InPost Gallery to the latest patched version immediately. If no patched version is available, remove 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. Check InPost Gallery plugin version
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Locate 'InPost Gallery' and read the version number displayed below the plugin name. Alternatively, use wp-cli: `wp plugin list --plugin=inpost-gallery --format=table` or inspect the plugin main file header at wp-content/plugins/inpost-gallery/inpost-gallery.php for the 'Version' field.
    Affected if The installed version is 2.1.4.6 or lower
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that InPost Gallery shows as 'Active'. From command line: `wp plugin status inpost-gallery`
    Affected if The plugin is installed and active, making the vulnerable code accessible to unauthenticated attackers
  3. Check for public-facing usage
    Visit the site homepage and common shortcode pages (e.g., pages using [inpost_gallery] shortcode) to confirm the plugin output is publicly accessible. Alternatively, scan the database wp_posts table for posts containing 'inpost_gallery' shortcode: `wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[inpost_gallery%' AND post_status='publish';"`
    Affected if The plugin shortcode or output is published on publicly accessible pages, allowing unauthenticated SQL injection exploitation

You are affected if InPost Gallery plugin version is 2.1.4.6 or below AND the plugin is active and publicly accessible on your site.

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 InPost Gallery to the latest patched version immediately. If no patched version is available, remove 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 / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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