← WordPress Vulnerabilities
WordPress security by component

ListingPro

ListingPro is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Jul 23, 2026; the highest CVE/CNA score is 9.3.

Plugin slug: listingpro-plugin

CVE-2026-65478: ListingPro: A security weakness

ListingPro is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.9.10.

PublishedJul 23, 2026
Known safe version> 2.9.10
Safe version
Jul 23, 2026 CVE-2026-65478
ListingPro: A security weakness
ListingPro is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.9.10.
> 2.9.10
CVE5.4
NVDPending
Jun 17, 2026 CVE-2026-39438
ListingPro: SQL injection
ListingPro is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data. The published affected range is n/a through 2.9.10.
2.9.11
CVE9.3
NVDPending
Mar 05, 2026 CVE-2026-28122
ListingPro: Cross-site scripting
ListingPro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE7.1
NVDPending
Dec 09, 2025 CVE-2025-63046
ListingPro: Cross-site scripting
ListingPro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.5
NVDPending
Sep 26, 2025 CVE-2025-60103
ListingPro: A security weakness
ListingPro is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.4
NVDPending