dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32120

HIGH · 7.6 CVSS v3.1 Published 2025-04-04
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 edanzer Easy Query – WP Query Builder easy-query allows Blind SQL Injection.This issue affects Easy Query – WP Query Builder: from n/a through <= 2.0.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 edanzer Easy Query – WP Query Builder WordPress plugin (versions up to 2.0.4). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through insufficient input sanitization in the plugin's query builder functionality. The 'blind' classification means attackers infer database information through application behavior changes rather than direct output.

MitigationUpdate to the latest patched version of the Easy Query plugin. If no update is available, implement parameterized queries using WordPress $wpdb->prepare() for all database interactions and apply proper input validation to all user-supplied 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
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 Easy Query plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'easy-query' or 'easy-query-wp-query-builder', or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The Easy Query plugin by edanzer appears in the site's plugin list
  2. Check installed plugin version
    In WordPress admin, view the plugin details to see the version number, or read the 'Version:' field in the plugin's main PHP file (usually easy-query.php or index.php inside the plugin folder)
    Affected if The installed version is 2.0.4 or any version lower than 2.0.4
  3. Confirm query builder functionality is enabled
    Check if the plugin's query builder shortcode or endpoint is actively used on the site, or attempt to access common query builder URLs (such as /?s=... with easy-query parameters). Review site pages and posts for [easy_query] shortcode usage
    Affected if The query builder feature (shortcode or endpoint) is present and accessible on the site
  4. Verify unauthenticated access is possible
    Test accessing the query builder functionality without logging in. Attempt to submit a query parameter through the plugin's front-end query builder interface without authentication
    Affected if The query builder accepts and processes requests from unauthenticated (logged-out) users

If the Easy Query plugin version 2.0.4 or lower is installed and the query builder feature is accessible to unauthenticated users, the environment is affected by this blind 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

Update to the latest patched version of the Easy Query plugin. If no update is available, implement parameterized queries using WordPress $wpdb->prepare() for all database interactions and apply proper input validation to all user-supplied parameters.

Recommended fix Moderate confidence

2.0.5 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Easy Query – WP Query Builder
  4. If the plugin shows version 2.0.4 or below, click Update Now
  5. After updating, verify the plugin version is 2.0.5 or higher

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