GeoDirectory place-category setting permits editor-level stored XSS
GeoDirectory before 2.8.110 stores a place-category setting without adequate sanitization and later renders it on an administrative page without output escaping. An Editor or another high-privilege user who is not allowed unfiltered_html can persist JavaScript that executes when a privileged user opens the affected page. This unscored record received deeper review because stored XSS can reach an administrator, including in multisite configurations. The CNA does not disclose the setting name, submission action or administrative page.
- Component
- GeoDirectory
- Plugin slug
geodirectory- Affected
- < 2.8.110
- Safe version
2.8.110- Published
- Aug 05, 2026
This CVE was published Aug 05, 2026 and is one of 23 known issues for this plugin.
Update, patch or deactivate.
Update GeoDirectory to 2.8.110 or later. Review place-category settings for unexpected markup and avoid opening untrusted settings pages in an administrator session until updated.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The GeoDirectory WordPress plugin before 2.8.110 does not sanitise and escape a place-category setting before outputting it back in an admin page, allowing high-privilege users such as editors and above to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in a multisite setup).
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N