GeoDirectory <= 2.8.181 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Text-type Custom Field (e.g., 'phone')

6.4
Improper Neutralization of Input During Web Page Generation
CVE CVE-2026-93897
CVSS 6.4 (Medium)
Publicly Published September 24, 2026
Last Updated September 25, 2026
Researcher Jonah Burgess (CryptoCat)

Description

The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Text-type Custom Field (e.g., 'phone') in all versions up to, and including, 2.8.181 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload must be stored in a text-type custom field (such as a phone field) via the AJAX geodir_save_post endpoint, using entity-encoded angle brackets (e.g., &lt;img src=x onerror=alert(1)&gt;) to bypass the strpos()-gated tag-stripping check.

Learn more about Cross-Site Scripting vulnerabilities and how to prevent them.

References

Share

Vulnerability Details for GeoDirectory – WP Business Directory Plugin and Classified Listings Directory

Software Type Plugin
Software Slug geodirectory (view on wordpress.org)
Patched? Yes
Remediation Update to version 2.8.182, or a newer patched version
Affected Version
  • <= 2.8.181
Patched Version
  • 2.8.182

Recent vulnerabilities in GeoDirectory – WP Business Directory Plugin and Classified Listings Directory

# Title CVE ID CVSS Researchers Date
1 GeoDirectory – WP Business Directory Plugin and Classified Listings Directory <= 2.8.202 - Unauthenticated Stored Cross-Site Scripting CVE-2026-124250 7.2 AndrewN November 9, 2026
2 GeoDirectory <= 2.8.200 - Unauthenticated Stored Cross-Site Scripting via Nested '[gd_dynamic_content]' Shortcode in post_content CVE-2026-120082 7.2 Kuba November 6, 2026
3 GeoDirectory <= 2.8.197 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'post_images' Image Title Delimiter Injection CVE-2026-116752 6.4 Mohamed Amgad Khater (mamgad) October 30, 2026
4 GeoDirectory <= 2.8.199 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'post_content' Parameter CVE-2026-119113 6.4 churchill11 October 30, 2026
5 GeoDirectory <= 2.8.198 - Unauthenticated Shortcode Injection via 'pagination_info' Parameter CVE-2026-118635 6.5 Wordfence PRISM October 30, 2026
6 GeoDirectory – WP Business Directory Plugin and Classified Listings Directory < 2.8.195 - Authenticated (Contributor+) Insecure Direct Object Reference CVE-2026-113494 4.3 Jacek Sowiński October 28, 2026
7 GeoDirectory – WP Business Directory Plugin and Classified Listings Directory < 2.8.196 - Authenticated (Contributor+) Stored Cross-Site Scripting CVE-2026-113487 6.4 Karthik Ramakrishnan October 28, 2026
8 GeoDirectory – WP Business Directory Plugin and Classified Listings Directory < 2.8.196 - Authenticated (Contributor+) Stored Cross-Site Scripting CVE-2026-113488 6.4 Karthik Ramakrishnan October 28, 2026
9 GeoDirectory <= 2.8.196 - Unauthenticated Information Exposure CVE-2026-114270 5.3 Erwan LR October 27, 2026
10 GeoDirectory <= 2.8.193 - Unauthenticated Information Exposure CVE-2026-113492 5.3 Jacek Sowiński October 22, 2026

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation