CVE-2026-39475
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 · uneditedImproper 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.1.
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 confidenceA blind SQL injection vulnerability exists in the User Feedback lite WordPress plugin (versions <= 1.10.1). The vulnerability stems from improper neutralization of special elements in SQL commands, allowing attackers to inject malicious SQL queries. Unlike standard SQL injection, blind SQLi does not return direct query results but instead infers information through behavioral differences in application responses.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm User Feedback plugin is installedAccess your WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'User Feedback' or 'userfeedback-lite' in the list of installed pluginsAffected if Plugin named 'User Feedback' or 'userfeedback-lite' appears in the installed plugins list
-
Check the installed version numberIn the Plugins list, locate the User Feedback plugin and note the version number displayed beneath the plugin name. Compare this to the affected version range (1.10.1 and below)Affected if Installed version is 1.10.1 or any version number lower than 1.10.1
-
Verify the plugin is activeIn WordPress Plugins > Installed Plugins, check if the User Feedback plugin shows as 'Active' rather than 'Inactive'Affected if Plugin status shows as Active
-
Confirm authentication is possibleCheck if user registration is enabled (Settings > General > Membership: Anyone can register) or if there are existing user accounts that could be compromised, as the vulnerability requires an authenticated attackerAffected if The site allows user registration or has user accounts that could provide attacker access
Your environment is affected if the User Feedback plugin (userfeedback-lite) is installed, active, and running version 1.10.1 or lower, with user authentication possible for an attacker to exploit the blind SQL injection.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of the User Feedback plugin. If no patched version is available, implement parameterized queries (prepared statements) for all database interactions and add input validation/sanitization for user-supplied data.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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