dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-68496

HIGH · 7.6 CVSS v3.1 Published 2025-12-24
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 Syed Balkhi User Feedback userfeedback-lite allows Blind SQL Injection.This issue affects User Feedback: from n/a through <= 1.10.0.

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

A blind SQL injection vulnerability exists in the User Feedback WordPress plugin (userfeedback-lite) through version 1.10.0. The vulnerability allows unauthenticated attackers to inject malicious SQL queries via unsanitized user input, potentially enabling data exfiltration from the database by inferring information through true/false responses or time-based delays.

MitigationUpdate the User Feedback plugin to the latest patched version. If no patch is available, disable the plugin until a fix is released. As a temporary mitigation, implement web application firewall rules to detect and block SQL injection attempts in plugin 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. Confirm User Feedback plugin installation
    Check for the plugin directory at wp-content/plugins/userfeedback-lite/ or look for 'User Feedback' in WordPress plugin admin panel
    Affected if The plugin directory exists or the plugin appears in WordPress admin
  2. Identify installed version
    Navigate to WordPress Admin > Plugins > User Feedback and view the version number displayed under the plugin name, or inspect the main plugin file header in wp-content/plugins/userfeedback-lite/userfeedback-lite.php
    Affected if Version is 1.10.0 or lower (any version up to and including 1.10.0 is affected)
  3. Verify plugin is active
    Check WordPress Admin > Plugins > Installed Plugins to confirm User Feedback shows as 'Active'
    Affected if Plugin status is Active (inactive plugins do not process requests, reducing attack surface)
  4. Inspect HTTP access logs for injection attempts
    Review web server access logs (Apache error.log, Nginx access.log, or WAF logs) for requests to /wp-admin/admin-ajax.php or plugin endpoints containing SQL meta-characters like quotes, UNION, SLEEP, or WHERE clauses in parameters
    Affected if Suspicious SQL injection patterns found in logs targeting plugin parameters

You are affected if the User Feedback plugin is installed, active, and running version 1.10.0 or lower, or if evidence of SQL injection attempts appears in your access logs.

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 the User Feedback plugin to the latest patched version. If no patch is available, disable the plugin until a fix is released. As a temporary mitigation, implement web application firewall rules to detect and block SQL injection attempts in plugin parameters.

Recommended fix Moderate confidence

UserFeedback Lite version 1.10.1 or later

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'User Feedback' (UserFeedback Lite) plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the fixed version from the WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin is working correctly and test the feedback submission functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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