# CVE-2026-111069: GeoDirectory WP Business Directory stored XSS in twitterusername

Source: https://junglewise.ai/threats/cve-2026-111069-the-geodirectory-wp-business-directory-plugin-and-classified  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-16. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-111069 · Severity: medium · CVSS 6.4 · Published 2026-10-16

GeoDirectory is a WordPress plugin that enables users to create business directories and classified listings. The plugin stores user-supplied Twitter usernames without proper validation, allowing authenticated subscribers to inject malicious scripts that execute when others view the directory pages, leading to account takeover, data theft, or malware distribution.

Technologies: [AyeCode GeoDirectory](https://junglewise.ai/threats/technologies/ayecode-geodirectory). Vendors: [AyeCode](https://junglewise.ai/threats/vendors/ayecode).

## Quick answers

**Is CVE-2026-111069 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111069 being exploited in the wild.

**How severe is CVE-2026-111069?** Medium severity, with a CVSS score of 6.4, published 16 October 2026.

**Which products and versions are affected?** AyeCode GeoDirectory up to and including 2.8.192.

**Is there a fix for CVE-2026-111069?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-111069 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-111069?** Check whether you run AyeCode GeoDirectory at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a stored cross-site scripting flaw in the 'twitterusername' parameter caused by insufficient server-side input sanitization and output escaping. An authenticated attacker with subscriber-level access can submit an attribute-breakout payload that bypasses the client-side alphanumeric pattern validation, storing arbitrary JavaScript in the custom field table that executes in the browser of any user viewing the affected listing.

## Affected products

- AyeCode GeoDirectory up to and including 2.8.192

## Timeline

- 2026-10-16: disclosed

## References

- [https://github.com/AyeCode/geodirectory/archive/refs/heads/master.zip](https://github.com/AyeCode/geodirectory/archive/refs/heads/master.zip)
- [https://plugins.trac.wordpress.org/browser/geodirectory/tags/2.8.192/includes/class-geodir-ajax.php](https://plugins.trac.wordpress.org/browser/geodirectory/tags/2.8.192/includes/class-geodir-ajax.php)

## Related threats

- [GeoDirectory stored cross-site scripting in post content](https://junglewise.ai/threats/cve-2026-120082-the-geodirectory-wp-business-directory-plugin-and-classified)
- [GeoDirectory stored cross-site scripting in post_images parameter](https://junglewise.ai/threats/cve-2026-116752-the-geodirectory-wp-business-directory-plugin-and-classified)
- [GeoDirectory WP Business Directory stored cross-site scripting in listing description](https://junglewise.ai/threats/cve-2026-119113-the-geodirectory-wp-business-directory-plugin-and-classified)
- [GeoDirectory arbitrary shortcode execution](https://junglewise.ai/threats/cve-2026-118635-the-the-geodirectory-wp-business-directory-plugin-and-classified)
- [GeoDirectory local file inclusion via design_type parameter](https://junglewise.ai/threats/cve-2026-104899-the-geodirectory-wp-business-directory-plugin-and-classified)