CVE-2026-39438

ListingPro Plugin <= 2.9.10 - Unauthenticated SQL Injection

2026-04-21 00:00
Phat RiO

Strategic Overview

Status
Patched in 2.9.11
Affected Plugin
ListingPro Plugin
Affected Version
<= 2.9.10
CVSS
7.5High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-39438
View all ListingPro Plugin vulnerabilities

At a glance

CVE-2026-39438 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the ListingPro Plugin WordPress plugin, affecting versions <= 2.9.10. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.9.11; sites on affected versions should update now. Disclosed April 2026, reported by Phat RiO.

Vulnerability Overview

The ListingPro Plugin plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 2.9.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers 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 privileges on the target site, 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 ListingPro Plugin <= 2.9.10 takes no account at all. 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 ListingPro Plugin the fix is 2.9.11: builds <= 2.9.10 are affected, anything from 2.9.11 onward is not.

Remediation

Update to version 2.9.11, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ListingPro Plugin 2.9.11 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-39438https://www.wordfence.com/threat-intel/vulnerabilities/id/6ee6abb4-eeb7-4ea3-912d-cb86d189b3bfhttps://nvd.nist.gov/vuln/detail/CVE-2026-39438

Related records

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