GEODIRECTORY · CVE-2026-120082 · Package
FIX → 2.8.201 ✓ verified
The GeoDirectory WordPress directory plugin does not sanitize the post_content parameter well enough, so unauthenticated attackers can store scripts in pages. Those scripts run in the browser of any user who opens the injected page.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
WordPress sites running the GeoDirectory plugin at 2.8.200 or earlier are exposed, because unauthenticated requests can store a script in post_content that runs in any visitor's browser. Directory and classified-listing sites that accept public submissions are the ones to check. Sites without the plugin, or on 2.8.201 or later, can skip it.
Not affected if patched-2.8.201, plugin-not-installed
Who cares geodirectory, self-hosted, wordpress
Upgrade to 2.8.201
Update GeoDirectory to 2.8.201 or later (latest listed by the vendor: , 2026-11-04).
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content' parameter in all versions up to, and including, 2.8.200 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nested shortcode payload ([gd_dynamic_conten[gd_tags]t ...]) defeats the plugin's geodir_strip_shortcodes() guard because WordPress's strip_shortcodes() performs only a single pass over registered tags, and HTML-entity-encoded attributes in the resulting shortcode survive wp_kses_post() because kses inspects HTML tags rather than shortcode attribute values.
This page as ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
2.8.202NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.