Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104993 Overview
CVE-2026-104993 is a stored Cross-Site Scripting (XSS) vulnerability [CWE-79] in the GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress. The flaw affects all versions up to and including 2.8.188. It stems from insufficient input sanitization and output escaping on the email parameter tied to the Contact Email custom field (htmlvar_name). Authenticated attackers with subscriber-level access or higher can inject arbitrary web scripts into listing pages. Exploitation requires that an administrator has configured the Contact Email custom field to render on the public single-listing output page and subsequently approves the attacker's submitted listing.
Critical Impact
Injected JavaScript executes in the browser of every visitor viewing the compromised directory listing, enabling session theft, redirects, and admin-targeted account takeover.
Affected Products
- GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress
- All versions through 2.8.188
- WordPress sites exposing the Contact Email custom field on single-listing pages
Discovery Timeline
- 2026-10-10 - CVE-2026-104993 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-104993
Vulnerability Analysis
The vulnerability lives in GeoDirectory's custom-field rendering pipeline. When a listing submission includes a Contact Email custom field, the plugin stores the submitted value and later renders it on the public single-listing page. The rendering path does not apply sufficient output escaping, which allows HTML and JavaScript payloads supplied by a subscriber-level user to reach the browsers of other site visitors.
Exploitation requires two preconditions. First, an administrator must have added and configured the Contact Email custom field so it renders on the public single-listing output. Second, the administrator must approve the attacker's submitted listing. Once approved, the stored payload executes for every user that loads the listing page, including administrators.
Because the scope is Changed per the CVSS vector, injected scripts execute in the context of the WordPress site and can target authenticated administrator sessions.
Root Cause
The root cause is improper neutralization of input during web page generation. The relevant files identified in the plugin source tree include includes/class-geodir-post-data.php, includes/custom-fields/output-functions.php, and includes/post-functions.php. The Contact Email field value flows from user submission to the DOM without context-aware escaping suitable for HTML attribute or body contexts.
Attack Vector
An attacker registers or uses an existing subscriber account, submits a new directory listing, and places a JavaScript payload in the Contact Email field. After administrator approval, any visitor to the listing page triggers execution. The vulnerability is network-reachable and requires only low-privileged authentication plus the administrator-approval gate.
No verified proof-of-concept code is published. Refer to the Wordfence Vulnerability Report and the WordPress Geodirectory Changeset 3728472 for the specific code path and fix.
Detection Methods for CVE-2026-104993
Indicators of Compromise
- Directory listings containing <script>, onerror=, javascript:, or encoded HTML entities in the Contact Email field value stored in wp_geodir_* tables.
- Unexpected outbound requests from administrator browsers after visiting a GeoDirectory listing page.
- New or modified WordPress administrator accounts shortly after a subscriber-submitted listing is approved.
Detection Strategies
- Query the GeoDirectory custom-fields tables for stored field values containing HTML tags or JavaScript event handlers.
- Review web server access logs for subscriber accounts submitting listings with unusually long or encoded Contact Email values.
- Inspect rendered single-listing pages with a headless browser to flag unexpected inline scripts.
Monitoring Recommendations
- Enable WordPress audit logging for listing submissions, approvals, and user role changes.
- Monitor for new subscriber account registrations followed by rapid listing submissions.
- Alert on administrator sessions that trigger uncharacteristic REST or admin-ajax calls after loading public listing pages.
How to Mitigate CVE-2026-104993
Immediate Actions Required
- Update GeoDirectory to the version released after 2.8.188 that includes WordPress Geodirectory Changeset 3728472.
- Audit pending and recently approved listings for script payloads in the Contact Email field.
- Rotate credentials and sessions for any administrator who viewed suspect listings.
Patch Information
The maintainers addressed the issue in GeoDirectory changeset 3728472, which corrects the output escaping in includes/custom-fields/output-functions.php. Review the WordPress Geodirectory Custom Fields source to confirm the fixed function in your deployed version.
Workarounds
- Temporarily remove or disable the Contact Email custom field from the public single-listing output until the plugin is patched.
- Require administrator-level privileges for listing submission by disabling self-registration or restricting the subscriber role.
- Deploy a web application firewall rule that strips HTML tags from email and htmlvar_name parameters submitted to GeoDirectory endpoints.
# Configuration example: disable WordPress open registration via wp-config.php or Settings → General
wp option update users_can_register 0
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

