VYPR
Unrated severityNVD Advisory· Published Jun 16, 2026

WordPress ListingPro plugin <= 2.9.10 - SQL Injection vulnerability

CVE-2026-39438

Description

SQL injection in WordPress ListingPro plugin versions <= 2.9.10 allows unauthenticated attackers to interact with the database, potentially leading to data theft.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

SQL injection in WordPress ListingPro plugin versions <= 2.9.10 allows unauthenticated attackers to interact with the database, potentially leading to data theft.

Vulnerability

The ListingPro WordPress plugin, versions 2.9.10 and earlier, contains an unauthenticated SQL injection vulnerability. This flaw resides in an unspecified input parameter that is processed without proper sanitization, allowing an attacker to inject arbitrary SQL statements. The vulnerability is reachable without any authentication, making it accessible to any remote attacker.

Exploitation

An attacker can exploit this vulnerability by sending crafted HTTP requests containing malicious SQL payloads to the vulnerable endpoint. No prior authentication or user interaction is required. Due to the ease of exploitation and lack of authentication, this vulnerability is expected to be used in mass-exploit campaigns targeting thousands of sites simultaneously [1].

Impact

Successful exploitation allows an attacker to directly interact with the underlying database, enabling data exfiltration, modification, or deletion. The CVSS score of 9.3 reflects the critical severity, as the attacker can steal sensitive information such as user credentials, personal data, or site configurations [1].

Mitigation

The vulnerability is fixed in version 2.9.11 of the ListingPro plugin. Users are strongly advised to update immediately. For those unable to update, Patchstack provides a mitigation rule that blocks attacks until a patch is applied [1].

AI Insight generated on Jun 17, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.