GeoDirectory – WP Business Directory Plugin and Classified Listings Directory vulnerabilities
Plugin slug geodirectory · 52 known vulnerabilities · latest disclosed 2026-11-09 · WordPress.org page
Every listed vulnerability has a fix. Version 2.8.203 or later is not affected by any of them. If your site runs an older version, update it.
14 of 52 rated high or critical (CVSS 7 or more).
Known vulnerabilities in GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.2 | <= 2.8.202 | 2.8.203 | CVE-2026-124250 | 2026-11-09 | Advisory |
| High 7.2 | <= 2.8.200 | 2.8.201 | CVE-2026-120082 | 2026-11-06 | Advisory |
| Medium 6.4 | <= 2.8.197 | 2.8.198 | CVE-2026-116752 | 2026-10-30 | Advisory |
| Medium 6.4 | <= 2.8.199 | 2.8.200 | CVE-2026-119113 | 2026-10-30 | Advisory |
| Medium 6.5 | <= 2.8.198 | 2.8.199 | CVE-2026-118635 | 2026-10-30 | Advisory |
| Medium 6.4 | < 2.8.196 | 2.8.196 | CVE-2026-113488 | 2026-10-28 | Advisory |
| Medium 6.4 | < 2.8.196 | 2.8.196 | CVE-2026-113487 | 2026-10-28 | Advisory |
| Medium 4.3 | < 2.8.195 | 2.8.195 | CVE-2026-113494 | 2026-10-28 | Advisory |
| Medium 5.3 | <= 2.8.196 | 2.8.197 | CVE-2026-114270 | 2026-10-27 | Advisory |
| Medium 6.4 | <= 2.8.193 | 2.8.194 | CVE-2026-113493 | 2026-10-22 | Advisory |
| Medium 6.5 | <= 2.8.193 | 2.8.194 | CVE-2026-113491 | 2026-10-22 | Advisory |
| Medium 5.3 | <= 2.8.193 | 2.8.194 | CVE-2026-113492 | 2026-10-22 | Advisory |
| Medium 5.3 | <= 2.8.193 | 2.8.194 | CVE-2026-113490 | 2026-10-22 | Advisory |
| Medium 4.3 | <= 2.8.193 | 2.8.194 | CVE-2026-113489 | 2026-10-22 | Advisory |
| High 7.2 | <= 2.8.193 | 2.8.194 | CVE-2026-113673 | 2026-10-22 | Advisory |
| Medium 5.3 | <= 2.8.193 | 2.8.194 | CVE-2026-113674 | 2026-10-22 | Advisory |
| Medium 6.4 | <= 2.8.191 | 2.8.192 | CVE-2026-110703 | 2026-10-15 | Advisory |
| Medium 6.4 | <= 2.8.192 | 2.8.193 | CVE-2026-111069 | 2026-10-15 | Advisory |
| Medium 6.4 | <= 2.8.190 | 2.8.191 | CVE-2026-107650 | 2026-10-13 | Advisory |
| Medium 6.4 | <= 2.8.190 | 2.8.191 | CVE-2026-107754 | 2026-10-13 | Advisory |
| High 8.1 | <= 2.8.187 | 2.8.188 | CVE-2026-104899 | 2026-10-09 | Advisory |
| Medium 6.4 | <= 2.8.188 | 2.8.189 | CVE-2026-104993 | 2026-10-09 | Advisory |
| High 7.5 | <= 2.8.186 | 2.8.187 | CVE-2026-103913 | 2026-10-02 | Advisory |
| Medium 6.4 | <= 2.8.183 | 2.8.184 | CVE-2026-96766 | 2026-09-24 | Advisory |
| Medium 6.4 | <= 2.8.181 | 2.8.182 | CVE-2026-93897 | 2026-09-24 | Advisory |
| High 7.5 | <= 2.8.174 | 2.8.175 | CVE-2026-84813 | 2026-09-02 | Advisory |
| Medium 4.3 | <= 2.8.176 | 2.8.177 | CVE-2026-81271 | 2026-08-26 | Advisory |
| High 7.2 | <= 2.8.173 | 2.8.174 | CVE-2026-66604 | 2026-08-19 | Advisory |
| Medium 6.4 | <= 2.8.177 | 2.8.178 | CVE-2026-68565 | 2026-08-18 | Advisory |
| High 8.1 | <= 2.8.169 | 2.8.170 | CVE-2026-19091 | 2026-08-11 | Advisory |
| Medium 5.3 | <= 2.8.168 | 2.8.169 | CVE-2026-16988 | 2026-08-03 | Advisory |
| Medium 4.4 | <= 2.8.109 | 2.8.110 | CVE-2025-15677 | 2026-07-28 | Advisory |
| Medium 4.3 | <= 2.8.167 | 2.8.168 | CVE-2026-16968 | 2026-07-27 | Advisory |
| Medium 6.4 | <= 2.8.161 | 2.8.162 | CVE-2026-57681 | 2026-06-30 | Advisory |
| High 7.5 | <= 2.8.162 | 2.8.163 | CVE-2026-54831 | 2026-06-17 | Advisory |
| Medium 5.3 | <= 2.8.157 | 2.8.158 | CVE-2026-42671 | 2026-05-13 | Advisory |
| High 7.5 | <= 2.8.152 | 2.8.154 | CVE-2026-39512 | 2026-04-13 | Advisory |
| Medium 4.3 | <= 2.8.149 | 2.8.150 | CVE-2026-24549 | 2026-01-23 | Advisory |
| Medium 4.3 | <= 2.8.139 | 2.8.140 | CVE-2025-12833 | 2025-11-11 | Advisory |
| Medium 6.4 | <= 2.8.119 | 2.8.120 | CVE-2025-6200 | 2025-06-20 | Advisory |
| Medium 6.4 | <= 2.8.97 | 2.8.98 | CVE-2024-13506 | 2025-02-10 | Advisory |
| High 7.5 | <= 2.8.97 | 2.8.98 | CVE-2024-13507 | 2025-01-29 | Advisory |
| Medium 6.4 | <= 2.3.84 | 2.3.85 | CVE-2024-56259 | 2024-12-30 | Advisory |
| Medium 6.4 | <= 2.3.80 | 2.3.81 | CVE-2024-50437 | 2024-10-24 | Advisory |
| Critical 9.9 | <= 2.3.61 | 2.3.62 | CVE-2024-43145 | 2024-08-07 | Advisory |
| Medium 6.4 | <= 2.3.48 | 2.3.49 | CVE-2024-3732 | 2024-04-22 | Advisory |
| Medium 6.6 | < 2.3.29 | 2.3.29 | CVE-2023-50845 | 2023-12-21 | Advisory |
| High 7.2 | <= 2.3.28 | 2.3.29 | none | 2023-10-18 | Advisory |
| High 7.2 | <= 2.2.23 | 2.2.24 | CVE-2023-0278 | 2023-01-31 | Advisory |
| Medium 6.4 | <= 2.2.21 | 2.2.22 | CVE-2022-4775 | 2022-12-29 | Advisory |
| Medium 4.1 | <= 2.2.19 | 2.2.20 | none | 2022-12-20 | Advisory |
| Medium 6.4 | <= 2.1.1.2 | 2.1.1.3 | CVE-2021-24720 | 2021-09-02 | Advisory |
Check if a site is affected
Enter a site address to see which version of GeoDirectory – WP Business Directory Plugin and Classified Listings Directory and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin safe to use?
All 52 known issues are fixed in current versions (2.8.203 or later). Keeping it updated is what matters.
How do I check which version of GeoDirectory – WP Business Directory Plugin and Classified Listings Directory my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.