WordPress security changelog
MEDIUM CVE-2026-93897 Deferred

GeoDirectory – WP Business Directory Plugin and Classified Listings Directory: Cross-site scripting

GeoDirectory (affected: <= 2.8.181). A Subscriber or higher can send entity-encoded markup in a text custom field, such as phone, through geodir_save_post AJAX. Encoding bypasses the strpos()-gated tag-stripping check, leaving a stored value that executes script when later rendered. The precise output function is unspecified.

CVE / CNA score 6.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
Plugin slug
geodirectory
Affected
<= 2.8.181
Safe version
2.8.182
Published
Sep 25, 2026
Weakness
CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This CVE was published Sep 25, 2026 and is one of 42 known issues for this plugin.

What to do

Update, patch or deactivate.

Update to 2.8.182 or a later supported release. The official changelog confirms remediation for this issue. Validate decoded custom-field values consistently and escape them at output, rather than deciding whether to sanitize based on a substring check.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical 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., <img src=x onerror=alert(1)>) to bypass the strpos()-gated tag-stripping check.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

References

Primary and upstream sources