CVE-2026-111069
Received Received - Intake

Stored XSS in GeoDirectory WordPress Plugin

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-111069
EUVD
EUVD-2026-102788

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Stored Cross-Site Scripting (XSS) vulnerability in the GeoDirectory WordPress plugin. It allows authenticated attackers with subscriber-level access or higher to inject malicious scripts via the 'twitterusername' parameter. The plugin fails to properly sanitize input and escape output, enabling stored XSS attacks that execute when users access affected pages.

Detection Guidance

Check WordPress sites using the GeoDirectory plugin for stored XSS via the 'twitterusername' parameter. Inspect custom field tables for malicious scripts in listings. Use security plugins like Wordfence to scan for suspicious inputs or obfuscated code in plugin files such as add-listing.min.js or geodirectory-plupload.js.

Impact Analysis

An attacker could steal user sessions, redirect users to malicious sites, or perform actions on their behalf. Since it requires only subscriber-level access, it poses a risk to any WordPress site using the vulnerable plugin versions up to 2.8.192.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. It may result in non-compliance due to potential data breaches or unauthorized access.

Mitigation Strategies

Update the GeoDirectory plugin to the latest version beyond 2.8.192. Implement strict input validation for the 'twitterusername' parameter. Use security plugins to block unauthorized script injections. Remove any suspicious listings or custom fields containing scripts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111069. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart