The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'email (Contact Email custom field htmlvar_name)' parameter in all versions up to, and including, 2.8.188 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. Successful exploitation requires that an administrator has added and configured the Contact Email custom field to render on the public single-listing output page, and that the administrator subsequently approves the attacker's submitted listing.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 6.4NVD modified 2026-10-13 13:30
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/AyeCode/geodirectory/archive/refs/heads/master.zip
- https://plugins.trac.wordpress.org/browser/geodirectory/tags/2.8.188/includes/class-geodir-post-data.php#L949
- https://plugins.trac.wordpress.org/browser/geodirectory/tags/2.8.188/includes/custom-fields/output-functions.php#L1448
- https://plugins.trac.wordpress.org/browser/geodirectory/tags/2.8.188/includes/post-functions.php#L1845
- https://plugins.trac.wordpress.org/changeset/3728472/geodirectory/trunk/includes/custom-fields/output-functions.php
- https://www.wordfence.com/threat-intel/vulnerabilities/id/1356ec70-4264-4687-8082-7d87a8978082?source=cve