Quick answers
- Is CVE-2026-39438 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39438 being exploited in the wild.
- How severe is CVE-2026-39438?
- Critical severity, with a CVSS score of 9.3, published 17 June 2026.
- Which products and versions are affected?
- ListingProWP ListingPro <= 2.9.10.
- Is there a fix for CVE-2026-39438?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-39438 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-39438?
- Check whether you run ListingProWP ListingPro at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The ListingPro plugin for WordPress is vulnerable to an unauthenticated SQL injection due to improper neutralization of special elements used in an SQL command (CWE-89). The vulnerability exists in versions up to and including 2.9.10. Because the flaw is reachable by unauthenticated users over the network, an attacker can send crafted requests to the application to execute arbitrary SQL queries. This can result in the extraction of sensitive data from the database or partial impact on service availability. The issue is resolved in version 2.9.11.
Affected products
- Emraan Cheema ListingPro <= 2.9.10
Timeline
- 2026-02-14: other: Vulnerability reported by Phat RiO
- 2026-04-21: advisory: Patchstack published advisory
- 2026-06-17: disclosed: CVE published to NVD