GeoDirectory <= 2.8.190 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Dynamic Content Field-Token Substitution via Listing Title
Strategic Overview
- Status
- Patched in 2.8.191
- Affected Version
<= 2.8.190- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-107650
At a glance
CVE-2026-107650 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the GeoDirectory WordPress plugin, affecting versions <= 2.8.190. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.8.191; sites on affected versions should update now. Disclosed October 2026, reported by Adrien Brunner.
Vulnerability Overview
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_title' parameter in all versions up to, and including, 2.8.190 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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
GeoDirectory <= 2.8.190 carries this weakness at post_title, and reaching it takes an account at Subscriber level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For GeoDirectory the fix is 2.8.191: builds <= 2.8.190 are affected, anything from 2.8.191 onward is not.
Remediation
Update to version 2.8.191, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GeoDirectory 2.8.191 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-66604: GeoDirectory Stored XSS
CVE-2026-66604 - 6.4CVE-2026-110703: GeoDirectory <= 2.8.191 Stored Cross-Site Scripting
CVE-2026-110703 - 6.4CVE-2026-111069: GeoDirectory <= 2.8.192 Stored Cross-Site Scripting
CVE-2026-111069 - 6.4CVE-2026-107754: GeoDirectory <= 2.8.190 Stored Cross-Site Scripting
CVE-2026-107754
Other vulnerabilities in GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
- 9.9CVE-2024-43145: GeoDirectory <= 2.3.61 SQL Injection
CVE-2024-43145 - 8.1CVE-2026-104899: GeoDirectory <= 2.8.187 Local File Inclusion
CVE-2026-104899 - 8.1CVE-2026-19091: GeoDirectory <= 2.8.169 Arbitrary File Deletion
CVE-2026-19091 - 7.5CVE-2026-103913: GeoDirectory <= 2.8.186 SQL Injection
CVE-2026-103913 - 7.5CVE-2026-84813: GeoDirectory SQL Injection
CVE-2026-84813 - 7.5CVE-2026-54831: GeoDirectory SQL Injection
CVE-2026-54831 - 7.5CVE-2026-39512: GeoDirectory SQL Injection
CVE-2026-39512 - 7.5CVE-2024-13507: GeoDirectory SQL Injection
CVE-2024-13507
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C