Live › vulnerability › CVE-2026-111069
Go to dashboardThe GeoDirectory WordPress plugin does not sanitize the twitterusername field on listings, so a subscriber-level user can store a script payload. The script runs in the browser of any visitor who opens the injected page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running GeoDirectory (WP Business Directory / Classified Listings Directory) at version 2.8.192 or earlier where subscribers or other low-privilege users can submit listings with the Twitter username field. The flaw depends on the server accepting input that the browser form would normally block, so a site with only admin-created listings is less exposed.
No product ranges from the sources yet.
wp plugin get geodirectory --field=version; versions up to and including 2.8.192 are affected2.8.192 (the fixed version is unknown from the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-111069")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.