dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32681

HIGH · 8.5 CVSS v3.1 Published 2025-04-11
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 WP Guru Error Log Viewer error-log-viewer-wp allows Blind SQL Injection.This issue affects Error Log Viewer: from n/a through <= 1.0.5.

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 WP Guru Error Log Viewer plugin (error-log-viewer-wp) versions 1.0.5 and below. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration from the WordPress database.

MitigationUpdate the Error Log Viewer plugin to the latest version which contains proper input sanitization using WordPress prepared statements ($wpdb->prepare()) or equivalent parameterized queries to neutralize SQL injection vectors.

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 the plugin is installed
    Check if the error-log-viewer-wp or wp-guru-error-log-viewer directory exists in wp-content/plugins/
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Check the installed plugin version
    Open the main plugin PHP file (usually error-log-viewer-wp.php) and look for the Version header in the plugin comment block, or check the readme.txt file for the Version field
    Affected if The reported version is 1.0.5 or earlier (the summary indicates versions through 1.0.5 are affected)
  3. Confirm the error log viewing feature is enabled
    Check WordPress admin under Plugins > Installed Plugins to see if the error-log-viewer-wp plugin is activated
    Affected if The plugin is active and the error log viewing functionality is accessible to users
  4. Verify the vulnerability parameter is present
    Access the plugin functionality through its admin menu (typically under Tools or Settings) and identify if input parameters related to log filtering or viewing accept user input that could be used in SQL queries
    Affected if The plugin accepts user-supplied input in parameters used for log filtering or pagination without visible sanitization

You are affected if the plugin is installed, the version is 1.0.5 or earlier, and the error log viewing feature with unsanitized input parameters is active and accessible.

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 the Error Log Viewer plugin to the latest version which contains proper input sanitization using WordPress prepared statements ($wpdb->prepare()) or equivalent parameterized queries to neutralize SQL injection vectors.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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