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

Q: What is CVE-2026-111069?

CVE-2026-111069 is a medium-severity cross-site scripting vulnerability in paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Q: Is CVE-2026-111069 being exploited?

There is no known exploitation of CVE-2026-111069 in the wild and no public exploit code.

Q: How do I fix CVE-2026-111069?

No fix has been published for CVE-2026-111069 yet. Limit exposure of the affected software until one is available.

Medium 6.4 Published 16 Oct 2026 Updated 16 Oct 2026

Authenticated attackers can inject arbitrary scripts via the twitterusername field, leading to stored XSS execution for other users.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-111069?

CVE-2026-111069 is a medium-severity cross-site scripting vulnerability in paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-79

Which versions are affected by CVE-2026-111069?

How do I fix CVE-2026-111069?

No fix has been published for CVE-2026-111069 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-111069 being exploited?