dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-56012

HIGH · 8.5 CVSS v3.1 Published 2026-06-18
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 David Lingren Media LIbrary Assistant allows Blind SQL Injection. This issue affects Media LIbrary Assistant: from n/a through 3.35.

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

SQL injection vulnerability in the Media Library Assistant WordPress plugin allows unauthenticated attackers to inject malicious SQL queries via unsanitized user input. The 'Blind' classification means the attacker cannot see direct query output but can infer results through behavioral differences in application responses.

MitigationUpgrade to Media Library Assistant version 3.36 or later. If patching is not immediately possible, implement WAF rules to detect and block SQL injection patterns in plugin request parameters.

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. Verify Media Library Assistant plugin is installed
    Check the WordPress plugins directory for the media-library-assistant folder, or run 'wp plugin list' via WP CLI to list installed plugins
    Affected if The plugin folder exists in wp-content/plugins/ and the plugin is listed as installed
  2. Determine the installed plugin version
    Open wp-content/plugins/media-library-assistant/readme.txt and locate the 'Stable tag' entry, or check the plugin header in the main PHP file for the 'Version' comment
    Affected if The version is below 3.36 (versions 3.35 and earlier are vulnerable)
  3. Confirm the plugin is active on the site
    Run 'wp plugin status media-library-assistant' via WP CLI, or check the WordPress admin Plugins page to verify the plugin is activated
    Affected if The plugin is active and running in a production environment
  4. Inspect server logs for SQL injection attempts
    Review web server access logs (Apache/Nginx) and WordPress debug logs for unusual query patterns in MLA-related parameters, particularly in request URLs containing 'mla' or 'attachment'
    Affected if Log entries show SQL injection patterns or unusual MLA-related database queries from unknown sources
  5. Check database for signs of exploitation
    Query the wp_options table or other critical tables for unexpected entries that may indicate SQL injection results were stored, or review recent database changes via query logs
    Affected if Unexpected records appear in tables that the plugin does not normally modify, or unauthorized admin users exist

A site is affected if Media Library Assistant version 3.35 or earlier is installed and active, exposing the plugin's SQL injection vulnerability to unauthenticated attackers.

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 Media Library Assistant version 3.36 or later. If patching is not immediately possible, implement WAF rules to detect and block SQL injection patterns in plugin request parameters.

Recommended fix Moderate confidence

Latest version of Media Library Assistant (version 3.36 or higher)

  1. Identify the currently installed Media Library Assistant version in WordPress via Plugins page
  2. Check if the installed version is 3.35 or lower
  3. Navigate to Plugins > Add New > Upload Plugin or use FTP to upload the latest version of Media Library Assistant
  4. Backup the WordPress database and files before upgrading
  5. Deactivate the current Media Library Assistant plugin
  6. Delete the current plugin files
  7. Upload and install the latest version from the official WordPress repository
  8. Reactivate the plugin and verify functionality
Caveat Minor release upgrade; review changelog for any deprecated features

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 / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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