CVE-2026-111069: GeoDirectory <= 2.8.192 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'twitterusername' Custom Field

Published Oct 16, 2026
·
Updated

The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'twitterusername' parameter in all versions up to, and including, 2.8.192 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 client-side HTML pattern attribute enforcing alphanumeric-only input on the twitterusername field is not validated server-side, allowing a listing owner with Subscriber-level access to submit an attribute-breakout payload that bypasses sanitization and is stored directly to the custom field table.

Affected Software

1 affected component
GeoDirectory GeoDirectory<=2.8.192

Event History

Oct 16, 2026
CVE Published
via MITRE·06:41 AM
Data Sourced
via MITRE·06:41 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs an authenticated WordPress account with Subscriber-level access or higher and must be able to submit or own a listing containing the twitterusername custom field. The issue does not require victim interaction from the attacker beyond a user later viewing the injected page.

2

Are installations running version 2.8.192 affected?

Yes. The affected range includes all GeoDirectory versions up to and including 2.8.192.

3

What is required for the injected script to execute?

The malicious value is stored in the twitterusername custom field and executes when another user accesses a page where the injected value is rendered. The browser-side alphanumeric pattern does not prevent exploitation because equivalent validation is not enforced server-side.

4

How can administrators check for possible exploitation?

Review values stored for the twitterusername custom field, particularly on listings owned by low-privileged users, for unexpected characters or HTML attribute-breakout and script payloads. Investigate affected listing pages that may render those stored values.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203