CVE-2026-111069 json
GeoDirectory <= 2.8.192 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'twitterusername' Custom Field
published 24d ago modified 24d ago also EUVD-2026-102788
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-111069 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/32052509-2fa6-4317-8861-314e6da0869f?source=cve
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.192/includes/custom-fields/output-filter-functions.php#L42
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.192/includes/class-geodir-ajax.php#L821
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.192/includes/class-geodir-post-data.php#L1661
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.192/includes/class-geodir-post-data.php#L450
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.192/includes/post-functions.php#L1950
- github.com /AyeCode/geodirectory/archive/refs/heads/master.zip
- plugins.trac.wordpress.org /changeset/3748786/geodirectory/trunk/includes/custom-fields/output-filter-functions.php
Sources
- CVE List CVE-2026-111069
- NVD CVE-2026-111069
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.