geodirectory vulnerabilities and fixes
Recent CVEs affecting geodirectory, with upgrade or downgrade steps. 5 tracked.
geodirectory has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2025-07-11. Highest priority: CVE-2024-43145 (score 39/100).
- CVE-2025-6200 MEDIUM 5.9 UPGRADE The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attribute
- CVE-2024-56259 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paolo Ge
- CVE-2024-50437 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paolo Ge
- CVE-2024-43981 MEDIUM 4.3 UPGRADE Missing Authorization vulnerability in AyeCode – WP Business Directory Plugins GeoDirectory allows Exploiting
- CVE-2024-43145 HIGH 8.5 UPGRADE Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AyeCode
FAQ
How do I fix geodirectory vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is geodirectory being exploited right now?
None of the tracked geodirectory CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which geodirectory CVE should I patch first?
CVE-2024-43145 currently ranks highest (39/100): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AyeCode .