---
id: "CVE-2026-111069"
kind: "vulnerability"
aliases: ["CVE-2026-111069"]
title: "GeoDirectory WordPress plugin: stored XSS via Twitter username field"
severity: "medium"
cvss: 6.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["geodirectory", "package", "self-hosted", "wordpress", "wordpress-plugin"]
not_affected_if: ["admin-only-listings", "default-config"]
published_at: "2026-10-16T07:17:11+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:59:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111069", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# GeoDirectory WordPress plugin: stored XSS via Twitter username field

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed GeoDirectory plugin version in the WordPress admin plugins list or with `wp plugin get geodirectory --field=version`; versions up to and including `2.8.192` are affected
- Confirm whether subscriber accounts can create or edit directory listings

## Fix

- Update the GeoDirectory plugin to a version later than `2.8.192` (the fixed version is unknown from the sources)
- Until updated, restrict listing submission to trusted roles

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-111069

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_