CVE-2026-39475

User Feedback <= 1.10.1 - Authenticated (Editor+) SQL Injection

2026-02-20 00:00
Nguyen Ba Khanh

Strategic Overview

Status
Patched in 1.11.0
Affected Plugin
UserFeedback – Create Interactive Feedback Form, User Surveys, and Polls in Seconds
Affected Version
<= 1.10.1
CVSS
4.9Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-39475
View all UserFeedback – Create Interactive Feedback Form, User Surveys, and Polls in Seconds vulnerabilities

At a glance

CVE-2026-39475 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the UserFeedback WordPress plugin, affecting versions <= 1.10.1. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 1.11.0; sites on affected versions should update now. Disclosed February 2026, reported by Nguyen Ba Khanh.

Vulnerability Overview

The User Feedback plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 1.10.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with editor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in UserFeedback <= 1.10.1 takes an account at Editor level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For UserFeedback the fix is 1.11.0: builds <= 1.10.1 are affected, anything from 1.11.0 onward is not.

Remediation

Update to version 1.11.0, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: UserFeedback 1.11.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-39475https://www.wordfence.com/threat-intel/vulnerabilities/id/40186505-3031-44e7-90ae-f013750c7ea1https://nvd.nist.gov/vuln/detail/CVE-2026-39475

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C